Setting data group auditing values manually - 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

Default behavior for MIMIX is to change the auditing value of IFS, DLO, and library-based objects configured for system journal replication as needed when starting data groups with the Start Data Group (STRDG) command.

To manually set the system auditing level of replicated objects, or to force a change to a lower configured level, you can use the Set Data Group Auditing (SETDGAUD) command.

The SETDGAUD command allows you to set the object auditing level for all existing objects that are defined to MIMIX by data group object entries, data group DLO entries, and data group IFS entries. The SETDGAUD command can be used for data groups configured for replicating object information (type *OBJ or *ALL).

When to set object auditing values manually - If you anticipate a delay between configuring data group entries and starting the data group, you should use the SETDGAUD command before synchronizing data between systems. Doing so will ensure that replicated objects will be properly audited and that any transactions for the objects that occur between configuration and starting the data group will be replicated.

You can also use the SETDGAUD command to reset the object auditing level for all replicated objects if a user has changed the auditing level of one or more objects to a value other than what is specified in the data group entries.

Processing options - MIMIX checks for existing objects identified by data group entries for the specified data group. The object auditing level of an existing object is set to the auditing value specified in the data group entry that most specifically matches the object. Default behavior is that MIMIX only changes an object’s auditing value if the configured value is higher than the object’s existing value.

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.

You can optionally force a change to a configured value that is lower than the existing value through the command’s Force audit value (FORCE) parameter.

  • The default value *NO for the FORCE parameter prevents MIMIX from reducing the auditing level of an object. For example, if the SETDGAUD command processes a data group entry with a configured object auditing value of *CHANGE and finds an object identified by that entry with an existing auditing value of *ALL, MIMIX does not change the value.

  • If you specify *YES for the FORCE parameter, MIMIX will change the auditing value even if it is lower than the existing value.

For IFS objects, it is particularly important that you understand the ramifications of the value specified for the FORCE parameter. For more information see Examples of changing of an IFS object’s auditing value.

Procedure -To set the object auditing value for a data group, do the following on each system defined to the data group:

  1. Type the command SETDGAUD and press F4 (Prompt).

  2. The Set Data Group Auditing (SETDGAUD) appears. Specify the name of the data group you want.

  3. At the Object type prompt, specify the type of objects for which you want to set auditing values.

  4. If you want to allow MIMIX to force a change to a configured value that is lower than the object’s existing value, specify *YES for the Force audit value prompt.

    Note: This may affect the operation of your replicated applications. We recommend that you force auditing value changes only when you have specified *ALLIFS for the Object type.
  5. Press Enter.

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

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