Default and legacy methods of cooperative processing have unique requirements for data group definitions as well as many common requirements for data group object entries and file entries, as indicated in Table 16. In both configurations, you must have:
-
A data group definition which specifies the required values.
-
One or more data group object entries that specify the required values. These entries identify the items within the name space for replication. You may need to create additional entries to achieve the desired results, including entries which specify a Process type of *EXCLD.
-
The identified existing objects must be journaled to the journal defined for the data group.
-
Data group file entries for the items identified by data group object entries. Processing cannot occur without these corresponding data group file entries.
| Critical Parameters | Required Values for Type of Cooperative Processing | Configuration Notes | ||
| Default | Legacy | |||
|
Data Group Definition |
||||
|
Data group type (TYPE) |
*ALL or *DB |
*ALL |
See Requirements and limitations of default cooperative processing for files. |
|
| Use remote journal link (RJLNK) |
*YES |
any value | ||
|
Cooperative journal (COOPJRN) |
*USRJRN | *SYSJRN | ||
|
File and tracking ent. opts: (FEOPT) Replication type |
*POSITION or *KEYED1 | any value | See Requirements and limitations of default cooperative processing for files | |
|
Data Group Object Entries |
||||
|
Object type (OBJTYPE) |
*ALL or *FILE |
*ALL or *FILE |
||
| Attribute (OBJATR) | *ALL or one of the following: LF, LF38, PF-DTA, PF-SRC, PF38-DTA, PF38-SRC | *ALL, PF-DTA, or PF38-DTA | ||
| Cooperate with database (COOPDB) |
*YES |
*YES |
See Corresponding data group file entries required. | |
| Cooperating object types (COOPTYPE) |
*FILE 2 |
*FILE 2 |
||
|
File and tracking ent. opts: (FEOPT) Replication type |
*DGDFT, or any value3 |
any value | See Requirements and limitations of default cooperative processing for files. | |
|
1The value *POSITION is required and cannot be changed in data groups that are configured to use multithreaded database apply processing. 2When creating new data group object entries, the value *DFT includes *FILE objects. 3In multithreaded configurations (shipped default) the value *DGDFT cannot be changed and resolves to *POSITION. In configurations that do not use multithreaded database apply processing, any value is supported. |
Corresponding data group file entries - Existing files identified by a data group object entry which specifies *YES for the Cooperate with DB (COOPDB) parameter must also be identified by data group file entries.
When a file is identified by both a data group object entry and an data group file entry, the following are also required:
-
If name mapping is used between systems, the data group object entry and file entry must have the same name mapping defined.
-
If the data group object entry and file entry specify different values for the File and tracking ent. opts (FEOPT) parameter, the values specified in the data group file entry take precedence.
-
Files defined by data group file entries must have journaling started and must be synchronized. If journaling is not started, MIMIX cannot replicate activity for the file.
Typically, data group object entries are created during initial configuration and are then used as the source for loading the data group file entries. The #DGFE audit can be used to determine whether corresponding data group file entries exist for the files identified by data group object entries.