Effect of omitting content on audits and comparison commands    - 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

Omitting T-ZC entries for *FILE, *DTAARA, or *DTAQ objects replicated by the system journal may affect whether the replicated objects on the source and target nodes are identical.

For example, recall how a file with an object auditing attribute value of *NONE is processed. After MIMIX replicates the initial creation of the file through the system journal, the file on the target system reflects the original state of the file on the source system when it was retrieved for replication. However, any subsequent changes to file data are not replicated to the target system. According to the configuration information, the files are synchronized between source and target systems, but the files are not the same.

A similar situation can occur when OMTDTA is used to prevent replication of predetermined types of changes. For example, if *MBR is specified for OMTDTA, the file and member attributes are replicated to the target system but the member data is not. The file is not identical between source and target systems, but it is synchronized according to configuration. Comparison commands will report these attributes as *EC (equal configuration) even though member data is different. MIMIX audits, which call comparison commands with a data group specified, will have the same results.

When the content of *DTAQ objects is omitted from system journal replication, the attributes *DATACRC and *SIZE are not processed by the #OBJATR audit or when a data group is specified on the CMPOBJA command. Differences detected for these attributes are reported as *EC (equal configuration) even though the object content is different.

When the content of *DTAARA objects is omitted from system journal replication, the attribute *VALUE is not processed by the #OBJATR audit or when a data group is specified on the CMPOBJA command. Differences detected for this attribute are reported as *EC (equal configuration) even though the object content is different.

Consider how the following comparison commands behave when faced with non-identical files that are synchronized according to the configuration.

  • The Compare File Attributes (CMPFILA) command has access to configuration information from data group object entries for files configured for system journal replication. When a data group is specified on the command, or when the command is submitted by the #FILATR or #FILATRMBR audit, files that are configured to omit data will report those omitted attributes as *EC (equal configuration).

  • The Compare File Data (CMPFILDTA) command uses file selection rules (data group file entries), not library selection rules (data group object entries) for configuration information. As a result, when a data group is specified on the command, or when the command is submitted by the #FILDTA audit, any file objects configured for OMTDTA will not be compared.

  • The Compare Object Attributes (CMPOBJA) command can be used to compare a data area or data queue, and to check for the existence of a file on both systems and to compare its basic attributes (those which are common to all object types). This command never compares file-specific attributes or member attributes and should not be used to determine whether a file is synchronized. When a data group is specified on the command, or when the command is submitted by the #OBJATR audit, data areas and data queues configured to omit data will report those omitted attributes as *EC (equal configuration).

Running a comparison command without specifying a data group will report omitted attributes and content as *NE (not equal) because no configuration information is considered.