Conversion examples - 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

To illustrate a simple conversion, assume that the systems defined to data group KEYAPP are running on an IBM i. You use this data group for system journal replication of the objects in library PRODLIB. The data group has one data group object entry which has the following values:

LIB1(PRODLIB) OBJ1(*ALL) OBJTYPE(*ALL) PRCTYPE(*INCLD) COOPDB(*YES) COOPTYPE(*FILE)

Example 1 - You decide to use user journal replication for all *DTAARA and *DTAQ objects replicated with data group KEYAPP. You have confirmed that the data group definition specifies TYPE(*ALL) and does not need to change. After performing a controlled end of the data group, you change the data group object entry to have the following values:

LIB1(PRODLIB) OBJ1(*ALL) OBJTYPE(*ALL) PRCTYPE(*INCLD) COOPDB(*YES) COOPTYPE(*DFT)
Note: COOPTYPE (*DFT) is equivalent to specifying COOPTYPE(*FILE *DTAARA *DTAQ).

When the data group is started, object tracking entries are loaded for the data area and data queue objects in PRODLIB. Those objects will now be replicated from a user journal. Any other object types in PRODLIB continue to be replicated from the system journal.

Example 2 - You want to use user journal replication for data group KEYAPP but one data area, XYZ, must remain replicated from the system journal. You will need the data group object entry described in Example 1.

LIB1(PRODLIB) OBJ1(*ALL) OBJTYPE(*ALL) PRCTYPE(*INCLD) COOPDB(*YES) COOPTYPE(*DFT)

You will also need a new data group object entry that specifies the following so that data area XYZ can be replicated from the system journal:

 LIB1(PRODLIB) OBJ1(XYZ) OBJTYPE(*DTAARA) PRCTYPE(*INCLD) COOPDB(*NO)

Example 3 - You want to use user journal replication for objects with the IFS Directory IFSDIR but one object, abcXYZ, must remain replicated from the system journal. You will need to do the following:

  1. Run the Convert Data Group IFS Entries (CVTDGIFSE) command. See Running the CVTDGIFSE command. A tracking entry (IFSTE) is created for all IFS objects.

  2. Add the data group IFS entry for the one object, abcXYZ, that you do not want to replicate through the user journal:

    OBJ1('/ifsdir/abcXYZ') PRCTYPE(*INCLD) COOPDB(*NO)
  3. If the object previously was not journaled, but is now because CVTDGIFSE journaled it, end journaling for the object’s tracking entry:

    ENDJRNIFSE OBJ(('/ifsdir/abcXYZ'))
  4. Remove the object’s tracking entry:

    RMVDGIFSTE OBJ1('/ifsdir/abcXYZ')