Choices for selecting attributes to compare - 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 Attributes to compare parameter allows you to select which combination attributes to compare.

Each compare attribute command supports an extensive list of attributes. Each command provides the ability to select pre-determined sets of attributes (basic or extended), all supported attributes, as well as any other unique combination of attributes that you require.

The basic set of attributes is intended to compare attributes that provide an indication that the objects compared are the same, while avoiding attributes that may be different but do not provide a valid indication that objects are not synchronized, such as the create timestamp (CRTTSP) attribute. Some objects, for example, cannot be replicated using IBM's save and restore technology. Therefore, the creation date established on the source system is not maintained on the target system during the replication process. The comparison commands take this factor into consideration and check the creation date for only those objects whose values are retained during replication.

The extended set of attributes includes the basic set of attributes and some additional attributes.

The following topics list the supported attributes for each command:

All comparison attributes supported by a specific compare attribute command may not be applicable for all object types supported by the command. For example, CMPOBJA supports a large number of object types and related comparison attributes. There are many cases where a specific comparison attributes are only valid for a particular object type.

Comparison attributes not supported by a given object type are ignored. For example, auto-start job entries is a valid comparison attribute for object types of subsystem description (*SBSD). For all other object types selected as a result of running the report, the auto-start job entry attribute is ignored for object types that are not of type *SBSD.

If a data group is specified on a compare request, configuration data is used when comparing objects that are identified for replication through the system journal. If an object’s configured object auditing value (OBJAUD) is *NONE, its attribute changes are not replicated. When differences are detected on attributes of such an object, they are reported as *EC (equal configuration) instead of being reported as *NE (not equal).

If a data group that has data group entries configured to allow audits to ignore attribute differences is specified on a compare request, any detected differences for attributes ignored by auditing are reported as *IC (not equal based on configuration but attribute differences are configured to be ignored) or *IN (differences were detected but ignored according to ignored attribute configuration settings).

For *FILE, *DTAARA, or *DTAQ objects configured for replication through the system journal and configured to omit T-ZC journal entries, also see Effect of omitting content on audits and comparison commands .