Configuration requirements - data areas and data queues - 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

Replication of data areas and data queues using default configuration options for user journal replication processes require the following:

  • The data group and data group object entries must have the values shown in Table 17, which are shipped default values on the configuration commands.

  • Object tracking entries must exist for the objects identified by properly configured object entries. Typically these are created automatically when the data group is started.

  • Before starting replication of a data group that uses shipped default values, existing objects that are identified by object tracking entries must have journaling started on both the source and target systems. If the data group specifies *NO for journal on target (JRNTGT), only the source system objects must be journaled.

Note: If the data group uses the optional journal-centric configuration for objects of type *DTAARA or *DTAQ, data group object entries are generally not needed to replicate data areas or data queues journaled to the user journal of the data group. When a journal-centric data group is created from the Assure UI portal, MIMIX automatically creates the data group object tracking entries it needs. When a journal-centric data group is created from the native user interface, you must manually create the object tracking entries using default values on the LODDGOBJTE command.

For any data group object entries you create for data areas or data queues, consider the following:

  • You must have at least one data group object entry which specifies a a Process type of *INCLD. You may need to create additional entries to achieve the desired results. This may include entries which specify a Process type of *EXCLD.

  • When specifying objects in data group object entries, specify only the objects that need to be replicated. Specifying *ALL or a generic name for the System 1 object (OBJ1) parameter will select multiple objects within the library specified for System 1 library (LIB1).

  • It is possible to replicate only a *DTAARA or *DTAQ object and have its data omitted from replication. Because cooperative processing and omitting data content are mutually exclusive configuration choices, consider having a more generic object entry that selects multiple object types and allows cooperative processing and one or more additional object entries that identify specific *DTAARA or *DTAQ objects whose data will be omitted. For details, see Omitting object content from system journal replication.

  • When you create data group object entries, you can specify an object auditing value within the configuration. The configured object auditing value affects how MIMIX handles changes to attributes of library-based objects. It is particularly important for, but not limited to, objects configured for system journal replication. For objects configured for user journal replication, the configured value can affect MIMIX performance. For detailed information, see Configured object auditing value for data group entries.

    Table 1. Critical configuration parameters for replicating *DTAARA and *DTAQ objects from a user journal in a standard configuration

    Critical Parameters

    Required Values

    Configuration Notes

    Data Group Definition

    Data group type (TYPE)


    Cooperative journal (COOPJRN)


    Data Group Object Entry

    Cooperate with database (COOPDB)


    Cooperating object types (COOPTYPE)

    *DFT or *DTAARA


    The value *DFT includes *FILE, *DTAARA, and *DTAQ.

Additionally, if any of the following apply, see Planning for journaled IFS objects, data areas, and data queues for additional details:

  • Converting existing configurations - When converting an existing data group to use or add advanced journaling, you must consider whether user journals should be shared and whether data area or data queue objects should be replicated in a data group that also replicates database files.

  • Serialized transactions - If you need to serialize transactions for database files and data area or data queue objects replicated from a user journal, you may need to adjust the configuration for the replicated files. Serialization between database files and data areas or data queues is only possible in data groups configured for single-threaded database apply processing.

  • Apply session load balancing - One database apply session, session A, is used for all data area and data queue objects are replicated from a user journal. This apply session can become overloaded because it is also used for IFS objects configured for replication through the user journal. This apply session can also be used for files in a data group that uses single-threaded database apply processing, You may need to adjust the configuration accordingly.

  • User exit programs - If you use user exit programs that process user journal entries, you may need to modify your programs.