Managing object auditing values of objects eligible for replication - 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

The system journal replication path within MIMIX relies on entries placed in the system journal by IBM i object auditing functions. To ensure that objects configured for this replication path retain an object auditing value that supports replication, MIMIX evaluates and changes the objects’ auditing value when necessary.

To do this, MIMIX employs a configuration value that is specified on the Object auditing value (OBJAUD) parameter of data group entries (object, IFS, DLO) configured for the system journal replication path. When MIMIX determines that an object’s auditing value is lower than the configured value, it changes the object to have the higher configured value specified in the data group entry that is the closest match to the object. The OBJAUD parameter supports object audit values of *ALL, *CHANGE, or *NONE.

Note: MIMIX will not change the object auditing value of *FILE, *DTAARA, and *DTAQ objects that are identified by data group object entries configured for cooperative processing with database replication1. Also, MIMIX will not change the object auditing value of *DTAARA objects that are identified by data group object entries configured for omitting content during system journal replication2. MIMIX skips all T-ZC journal entries associated with these data areas.

MIMIX evaluates and may change an object’s auditing value when specific conditions exist during object replication or during processing of a Start Data Group (STRDG) request. This evaluation process can also be invoked manually for all objects identified for replication by a data group.

During replication - MIMIX may change the auditing value during replication when an object is replicated because it was created, restored, moved, or renamed into the MIMIX name space (the group of objects defined to MIMIX).

While starting a data group - MIMIX may change the auditing value while processing a STRDG request if the request specified processes that cause object send (OBJSND) jobs to start and the request occurred after a data group switch or after a configuration change to one or more data group entries (object, IFS, or DLO).

Shipped command defaults for the STRDG command allow MIMIX to set object auditing if necessary. If you would rather set the auditing level for replicated objects yourself, you can specify *NO for the Set object auditing level (SETAUD) parameter when you start data groups.

Invoking manually - The Set Data Group Auditing (SETDGAUD) command provides the ability to manually set the object auditing level of existing objects identified for replication by a data group. When the command is invoked, MIMIX checks the audit value of existing objects identified for system journal replication. Shipped default values on the command cause MIMIX to change the object auditing value of objects to match the configured value when an object’s actual value is lower than the configured value.

The SETDGAUD command is used during initial configuration of a data group. Otherwise, it is not necessary for normal operations and should only be used under the direction of a trained MIMIX support representative.

The SETDGAUD command also supports optionally forcing a change to a configured value that is lower than the existing value through its Force audit value (FORCE) parameter.

Evaluation processing - Regardless of how the object auditing evaluation is invoked, MIMIX may find that an object is identified by more than one data group entry within the same class of object (IFS, DLO, or library-based). It is important to understand the order of precedence for processing data group entries.

Data group entries are processed in order from most generic to most specific. IFS entries are processed using the unicode character set; object entries and DLO entries are processed using the EBCDIC character set.  The first entry (more generic) found that matches the object is used until a more specific match is found.  

The entry that most specifically matches the object is used to process the object. If the object has a lower audit value, it is set to the configured auditing value specified in the data group entry that most specifically matches the object.

When MIMIX processes a data group IFS entry and changes the auditing level of objects which match the entry, the object is checked and, if necessary, changed to the new auditing value. In the case of an IFS entry with a generic name, all descendants of the IFS object may also have their auditing value changed.

When you change a data group entry, MIMIX updates all objects identified by the same type of data group entry in order to ensure that auditing is set properly for objects identified by multiple entries with different configured auditing values. For example, if a new DLO entry is added to a data group, MIMIX sets object auditing for all objects identified by the data group’s DLO entries, but not for its object entries or IFS entries.

For more information and examples of setting auditing values with the SETDGAUD command, see Setting data group auditing values manually.

1.   For instances running MIMIX service pack 8.1.06.00 or earlier, this behavior applies only to cooperatively processed *FILE objects.

2.   This behavior is possible in instances running MIMIX service pack 8.1.07.00 or later.