Comparing file and member attributes - 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
2024
First publish date
1999
Last updated
2024-10-22
Published on
2024-10-22T10:04:43.803975

You can compare file attributes to ensure that files and members needed for replication exist on both systems or 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.

Note: If you have automation programs monitoring escape messages for differences in file attributes, be aware that differences due to active replication (Step 16) are signaled via a new difference indicator (*UA) and escape message. See the auditing and reporting topics in this book.

To compare the attributes of files and members, 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 1 (Compare file attributes) and press Enter.

  3. The Compare File Attributes (CMPFILA) command appears. At the Data group definition prompts, do one of the following:

    • To compare attributes 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 files by 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, 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 Comparison level prompt, accept the default to compare files at a file level only. Otherwise, specify *MBR to compare files at a member level.

    Note: If *FILE is specified, the Member prompt is ignored see Step 4b.
  7. At the Attributes to compare prompt, accept *BASIC to compare a pre-determined set of attributes based on whether the comparison is at a file or member level or press F4 to see a valid list of attributes.

  8. At the Attributes to omit prompt, accept *NONE to compare all attributes specified in Step 7, or enter the attributes to exclude from the comparison. Press F4 to see a valid list of attributes.

  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 Report type prompt, specify the level of detail for the output report.

  12. At the Output prompt, do one of the following

    • To generate print output, accept *PRINT and press Enter.

    • To generate both print output and an outfile, specify *BOTH and press Enter. Skip to Step 14.

    • To generate an outfile, specify *OUTFILE and press Enter. Skip to Step 14.

  13. The User data prompt appears if you selected *PRINT or *BOTH in Step 12. Accept the default to use the command name to identify the spooled output or specify a unique name. Skip to Step 18.

  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 Maximum replication lag prompt, specify the maximum amount of time between when a file in the data group changes and when replication of the change is expected to be complete, or accept *DFT to use the default maximum time of 300 seconds (5 minutes). You can also specify *NONE, which indicates that comparisons should occur without consideration for replication in progress.

    Note: This parameter is only valid when a data group is specified in Step 3.
  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, specify *CMD to use the command name to identify the job or specify a simple name.

  21. To start the comparison, press Enter.