Checklist: Change *DTAARA, *DTAQ, IFS objects to user journaling - assure_mimix - 10.0

Use this checklist to change the configuration of an existing data group so that IFS objects, *DTAARA and *DTAQ objects can be replicated from entries in a user journal. (This environment is also called advanced journaling.) The procedure in this checklist assumes that the data group already includes user journal replication for files.

Topic User journal replication of IFS objects, data areas, data queues describes the benefits and restrictions of replicating these objects from user journal entries. It also identifies the MIMIX processes used for replication and the purpose of tracking entries.

To convert existing data groups to user journaling, do the following:

1. Determine if IFS objects, data areas, and data queues should be replicated in a data group shared with other objects undergoing database replication, or if these objects should be in a separate data group. Topic Planning for journaled IFS objects, data areas, and data queues provides guidelines for the following planning considerations:

   • Serializing transactions with database files

   • Converting existing data groups, including examples

   • Database apply session balancing

   • User exit program considerations

2. Perform a controlled end of the data groups that will include objects to be replicated using advanced journaling. See the Assure MIMIX Operations book for how to end a data group in a controlled manner (ENDOPT(*CNTRLD)).

3. Ensure that all pending activity for objects and IFS objects has completed. Use the command WRKDGACTE STATUS(*ACTIVE) to display any pending activity entries. Any activities that are still in progress will be listed.

4. The data group definitions used for user journal replication of IFS objects, data areas, and data queues must specify *ALL as the value for Data group type (TYPE). Verify the value in the data group definition is correct. If necessary, change the value.

   Note: If you have to change the Data group type, the journal definitions and journaling environment for user journal replication may not exist. If necessary, create the journal definitions (Creating a journal definition) and build the journaling environment (Building the journaling environment).

5. Add or change data group IFS entries for the IFS objects you want to replicate. Be sure to specify *YES for the Cooperate with database prompt in procedure Adding or changing a data group IFS entry . For additional information, see Restrictions for user journal replication of IFS objects.

6. Add or change data group object entries for the data areas and data queues you want to replicate using the procedure Adding or changing a data group object entry. For additional information, see Restrictions - user journal replication of data areas and data queues .

   Note: New data group object entries automatically default to values that result in user journal replication of *DTAARA and *DTAQ objects.

7. Load the tracking entries associated with the data group IFS entries and data group object entries you configured. Use the procedures in Loading tracking entries.

8. Optionally, you can manually deploy data group configuration within MIMIX. Although MIMIX will automatically deploy configuration information when data groups are started, manually deploying is recommended for data groups with large amounts of configured IFS objects. Manual deploying allows you the opportunity to validate the list of objects to be replicated and the subsequent start of the data groups will be faster. Use the procedure Manually deploying configuration changes.

9. Start journaling using the following procedures as needed for your configuration. If you ever plan to switch the data groups, you must start journaling on both the source system and on the target system.

   • For IFS objects, use Starting journaling for IFS objects

   • For data areas or data queues, use Starting journaling for data areas and data queues

10. Verify that journaling is started correctly. This step is important to ensure the IFS objects, data areas and data queues are actually replicated. For IFS objects, see Verifying journaling for IFS objects . For data areas and data queues, see Verifying journaling for data areas and data queues .

11. If you anticipate a delay between configuring data group IFS, object, or file entries and starting the data group, use the SETDGAUD command before synchronizing data between systems. Doing so will ensure that replicated objects are properly audited and that any transactions for the objects that occur between configuration and starting the data group are replicated. Use the procedure Setting data group auditing values manually.

12. Synchronize the IFS objects, data areas and data queues between the source and target systems. For IFS objects, follow the Synchronize IFS Object (SYNCIFS) procedures. For data areas and data queues, follow the Synchronize Object (SYNCOBJ) procedures. Refer to chapter Synchronizing data between systems for additional information.

13. If you are replicating large amounts of data, you should specify IBM i journal receiver size options that provide large journal receivers and large journal entries. Journals created by MIMIX are configured to allow maximum amounts of data. Journals that already exist may need to be changed.

    a.After IFS objects are configured, perform the steps in Verifying journal receiver size options to ensure journaling is configured appropriately.

    b.Change any journal receiver size options necessary using Changing journal receiver size options .

14.    If you have database replication user exit programs, changes may need to be made. See User exit program considerations.

15. Once you have completed the preceding steps, start the data groups. For more information about starting data groups, see the Assure MIMIX Operations book.