Comparing file member data - basic procedure (non-active) - assure_mimix - 10.0

You can use the CMPFILDTA command to ensure that data required for replication exists on both systems and any time you need to verify that files are synchronized between systems. You can optionally specify that results of the comparison are placed in an outfile.

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.

To perform a basic data comparison, 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, do one of the following:

   • To compare data for all files defined by the data group file entries for a particular data group definition, specify the data group name and skip to Step 6.

   • To compare data by file name only, specify *NONE and continue with the next step.

   • To compare a subset of files defined to a data group, specify the data group name and continue with the next step.

4. At the File prompts, you can specify elements for one or more object selectors that either identify files to compare or 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. At the System 2 file and System 2 library prompts, if the file and library names on system 2 are equal to system 1, accept the defaults. Otherwise, specify the name of the file and library to which files on the local system are compared.

      Note: The System 2 file and System 2 library values are ignored if a data group is specified on the Data group definition prompts.

   6. Press Enter.

5. The System 2 parameter prompt appears if you are comparing files not defined to a data group. If necessary, specify the name of the remote system to which files on the local system are compared.

6. At the Repair on system prompt, accept *NONE to indicate that no repair action is done.

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

8. At the File entry status prompt, specify *ACTIVE to process only those file members that are active.

9. 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.

10. 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.

11. At the Subsetting option prompt, specify *ALL to select all data and to indicate that no subsetting is performed.

12. At the Report type prompt, do one of the following:

    • If you want all compared objects to be included in the report, accept the default.

    • If you only want objects with detected differences to be included in the report, specify *DIF.

    • If you want to include the member details and relative record number (RRN) of the first 1,000 objects that have differences, specify *RRN.

    Notes:

    • The *RRN value can only be used when *NONE is specified for the Repair on system prompt and *OUTFILE is specified for the Output prompt.

    • The *RRN value outputs to a unique outfile (MXCMPFILR). Specifying *RRN can help resolve situations where a discrepancy is known to exist but you are unsure which system contains the correct data. This value provides the information that enables you to display the specific records on the two systems and determine the system on which the file should be repaired.

13. 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 18.

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

14. 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.)

15. 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.

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

    Note: If *YES is specified on the Process while active prompt and *OUTFILE was specified on the Outfile prompt, you must select *SYS2 for the System to receive output prompt.

17. 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.

18. 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 continue with the next step.

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

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

21. To start the comparison, press Enter.