Ignoring attribute differences in distributed environments - 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

In MIMIX environments that distribute data between systems using non-switchable data groups or using data groups whose target node is a replicate node of an application group, you can configure which attributes of replicated objects will be ignored by audit error reporting. This capability helps to streamline distribution and limits audit error reporting for object attributes or data known to be different between systems.

To support this capability, selection rules (data group entries) that identify objects for replication must be also be configured to specify the object attributes or data for which any differences detected by audits can be ignored by audit error reporting. Data cannot be ignored for physical files (PF). If this capability is configured for a switchable data group, it is ignored by MIMIX.

When attributes of replicated objects are configured to be ignored by audits, MIMIX does the following:

  • Audits will ignore differences detected for the specified attributes and will not perform recovery actions for those attributes or report those differences as errors. Similarly, compare commands that specify a data group also will ignore differences for the specified attributes.

  • Any differences for the specified attributes will be maintained according to the default behavior of MIMIX synchronization requests. This includes requests made by audit recoveries. Default synchronization behavior is that ignored attributes will not be synchronized and will keep their current values on each system in the data group. Options exist in synchronize dialogs and commands to allow you to override this default behavior so that attributes ignored by auditing are included in a synchronization request.

The audits that compare attributes are: Libraries (#OBJATR), File Attributes (#FILATR), File Member Attributes (#FILATRMBR), Directories (#IFSATR), and Folders (#DLOATR). The resulting status values that you will see when these audits detect differences in the ignored attributes are:

  • An ignored attribute for which differences are detected has a compare phase status of either:

  • *IN - ignored not equal. Differences were detected and ignored because of attribute is configured to be ignored by auditing.

  • *IC - Ignored, not as configured). Values are not equal based on MIMIX configuration settings and ignored because of attribute is configured to be ignored by auditing

  • An object for which the most severe status is that one or more attributes have a status of *IC or *IN has an object audit status of Ignored Attributes (*IGN).

Note: An object with Ignored Attributes status will not be selected for a Differences audit run.
  • An audit for which the most severe status is that one or more objects have ignored attributes has an audit status of Differences Ignored (*IGNATR).

Configuration: You can specify attributes to be ignored by auditing when you create or change data group entries. Changes to existing entries are available for use by audits in the next audit run that selects the identified object.

For journal-centric configurations, ignored attributes need to have specific data group entries created to identify the objects and which attributes to ignore.

For information about how to configure data group entries to allow audits to ignore attribute differences, see the following topics:

Synchronization: For information about how to synchronize attributes that have been configured to be ignored by auditing, see the following topics: