Comparing and repairing file member data - members on hold (*HLDERR) - assure_mimix - 10.0

Assure MIMIX Administrator Reference

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure MIMIX™ Software
Version
10.0
Language
English
Product name
Assure MIMIX
Title
Assure MIMIX Administrator Reference
Copyright
2023
First publish date
1999
ft:lastEdition
2024-05-07
ft:lastPublication
2024-05-07T13:36:02.962500

Members that are being held due to error (*HLDERR) can be repaired with the Compare File Data (CMPFILDTA) command during active processing. When members in *HLDERR status are processed, the CMPFILDTA command works cooperatively with the database apply (DBAPY) process to compare and repair the members—and when possible, restore them to an active state.

Before you begin, see the recommendations, restrictions, and security considerations described in Considerations for using the CMPFILDTA command. You should also read Specifying CMPFILDTA parameter values for additional information about parameters and values that you can specify.

The following procedure repairs a member without transmitting the entire member. As such, this method is generally faster than other methods of repairing members in *HLDERR status that transmit the entire member or file. However, if significant activity has occurred on the source system that has not been replicated on the target system, it may be faster to synchronize the member using the Synchronize Data Group File Entry (SYNCDGFE) command.

To repair a member with a status of *HLDERR, do the following:

  1. From the MIMIX Intermediate Main Menu, select option 12 (Compare, verify, and synchronize menu) and press Enter.

  2. From the MIMIX Compare, Verify, and Synchronize menu, select option 7 (Compare file data) and press Enter.

  3. The Compare File Data (CMPFILDTA) command appears. At the Data group definition prompts, you must specify a data group name.

    Note: If you want to compare data for all files defined by the data group file entries for a particular data group definition, skip to Step 5.
  4. At the File prompts, you can optionally specify elements for one or more object selectors that act as filters to the files defined to the data group indicated in Step 3. For more information, see Object selection for Compare and Synchronize commands.

    You can specify as many as 300 object selectors by using the + for more prompt for each selector. For each selector, do the following:

    1. At the File and library prompts, specify the name or the generic value you want.

    2. At the Member prompt, accept *ALL or specify a member name to compare a particular member within a file.

    3. At the Object attribute prompt, accept *ALL to compare the entire list of supported attributes or press F4 to see a valid list of attributes.

    4. At the Include or omit prompt, specify the value you want.

    5. Press Enter.

      Note: The System 2 file and System 2 library values are ignored when a data group is specified on the Data group definition prompts.
  5. At the Repair on system prompt, specify *TGT    to indicate that repair action be performed on the target system.

  6. At the Process while active prompt, specify *YES to indicate that active processing technology should be used in the comparison.

  7. At the File entry status prompt, specify *HLDERR to process members being held due to error only.

  8. At the System 1 ASP group prompt, accept the default if no objects from any ASP group are to be compared on system 1. Otherwise, specify the name of the ASP group that contains objects to be compared on system 1.

    Note: This parameter is ignored when a data group definition is specified.
  9. At the System 2 ASP group prompt, accept the default if no objects from any ASP group are to be compared on system 2. Otherwise, specify the name of the ASP group that contains objects to be compared on system 2.

    Note: This parameter is ignored when a data group definition is specified.
  10. At the Output prompt, do one of the following:

    • To generate spooled output that is printed, accept the default, *PRINT. Press Enter and continue with the next step.

    • To generate an outfile and spooled output that is printed, specify *BOTH. Press Enter and continue with the next step.

    • If you do not want to generate output, specify *NONE. Press Enter and skip to Step 15.

    • To generate an outfile, specify *OUTFILE. Press Enter and continue with the next step.

  11. At the File to receive output prompts, specify the file and library to receive the output. (Press F1 (Help) to see the name of the supplied database file.)

  12. At the Output member options prompts, do the following:

    1. At the Member to receive output prompt, specify the name of the database file member to receive the output of the command.

    2. At the Replace or add prompt, specify whether new records should replace existing file members or be added to the existing list.

  13. At the System to receive output prompt, specify the system on which the output should be created.

  14. At the Object difference messages prompt, specify whether you want detail messages placed in the job log. The value *INCLUDE places detail messages in the job log, and is the default used outside of shipped rules. When used as part of shipped rules, the default value is *OMIT since the results are already placed in an outfile.

  15. At the Submit to batch prompt, do one of the following:

    • If you do not want to submit the job for batch processing, specify *NO and press Enter to start the comparison.

    • To submit the job for batch processing, accept the default. Press Enter.

  16. At the Job description and Library prompts, specify the name and library of the job description used to submit the batch request.

  17. At the Job name prompt, accept *CMD to use the command name to identify the job or specify a simple name.

  18. To compare and repair the file, press Enter.