Configured object auditing value for data group entries - assure_mimix - 10.0

Assure MIMIX Administrator Reference

Product type
Product family
Assure MIMIX™ Software
Product name
Assure MIMIX
Assure MIMIX Administrator Reference
First publish date

When you create data group entries for library-based objects, IFS objects, or DLOs, you can specify an object auditing value within the configuration. This configured object auditing value affects how MIMIX handles changes to attributes of objects. It is particularly important for, but not limited to, objects configured for system journal replication.

The Object auditing value (OBJAUD) parameter defines a configured object auditing level for use by MIMIX. This configured value is associated with all objects identified for processing by the data group entry. An object’s actual auditing level determines the extent to which changes to the object are recorded in the system journal and replicated by MIMIX. The configured value is used during initial configuration and during processing of requests to compare objects that are identified by configuration data.

In specific scenarios, MIMIX evaluates whether an object’s auditing value matches the configured value of the data group entry that most closely matches the object being processed. If the actual value is lower than the configured value, MIMIX sets the object to the configured value so that future changes to the object will be recorded as expected in the system journal and therefore can be replicated.

Note: MIMIX only considers changing an object’s auditing value when the data group object entry is configured for system journal replication. MIMIX does not change the object’s value for files, data areas, and data queues that are configured for cooperative processing

The configured value specified in data group entries can affect replication of some journal entries generated when an object attribute changes. Specifically, the configured value can affect replication of T-ZC journal entries for files and IFS objects and T-YC entries for DLOs. Changes that generate other types of journal entries are not affected by this parameter.

When MIMIX changes the audit level, the possible values have the following results:

  • The default value, *CHANGE, ensures that all changes to the object by all users are recorded in the system journal.

  • The value *ALL ensures that all changes or read accesses to the object by all users are recorded in the system journal. The journal entries generated by read accesses to objects are not used for replication and their presence can adversely affect replication performance.

  • The value *NONE results in no entries recorded in the system journal when the object is accessed or changed.

The values *CHANGE and *ALL result in replication of T-ZC and T-YC journal entries. The value *NONE prevents replication of attribute and data changes for the identified object or DLO because T-ZC and T-YC entries are not recorded in the system journal. For files configured for MIMIX Dynamic Apply and any IFS objects, data areas, or data queues configured for user journal replication, the value *NONE can improve MIMIX performance by preventing unneeded entries from being written to the system journal.

When a compare request includes an object with a configured object auditing value of *NONE, any differences found for attributes that could generate T-ZC or T-YC journal entries are reported as *EC (equal configuration).

You may also want to read the following: