Comparing DLO 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
2023
First publish date
1999
ft:lastEdition
2024-05-07
ft:lastPublication
2024-05-07T13:36:02.962500

You can compare DLO attributes to ensure that DLOs needed for replication exist on both systems or any time you need to verify that DLOs 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 DLO attributes, be aware that differences due to active replication (Step 13) 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 DLOs, 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 4 (Compare DLO attributes) and press Enter.

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

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

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

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

  4. At the Document library objects prompts, you can specify elements for one or more object selectors that either identify DLOs to compare or that act as filters to the DLOs 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 DLO path name prompt, accept *ALL or specify the name or the generic value you want.

    2. At the Folder subtree prompt, accept *NONE or specify *ALL to define the scope of IFS objects to be processed.

    3. At the Name pattern prompt, specify a value if you want to place an additional filter on the last component of the DLO path name.

      Note: The *ALL default is not valid if a data group is specified on the Data group definition prompts.
    4. At the DLO type prompt, accept *ALL or specify a specific DLO type to compare.

    5. At the Owner prompt, accept *ALL or specify the owner of the DLO.

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

    7. At the System 2 DLO path name and System 2 DLO name pattern prompts, if the DLO path name and name pattern on system 2 are equal to system 1, accept the defaults. Otherwise, specify the name of the path name and pattern to which DLOs on the local system are compared.

      Note: The System 2 DLO path name and System 2 DLO name pattern values are ignored if a data group is specified on the Data group definition prompts.
    8. Press Enter.

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

  6. At the Attributes to compare prompt, accept *BASIC to compare a pre-determined set of attributes or press F4 to see a valid list of attributes.

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

  8. At the Report type prompt, specify the level of detail for the output report.

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

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

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

  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 Maximum replication lag prompt, specify the maximum amount of time between when a DLO 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.
  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 continue with the next step.

  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 start the comparison, press Enter.