Data group object entries are used to identify library-based objects for replication. How replication is performed for the objects identified depends on the object type and configuration settings. For detailed concepts and requirements for supported configurations, see the following topics:
-
For object types that cannot be journaled to a user journal, system journal replication processes are used. See Identifying library-based objects for replication.
-
For object types that can be journaled (*FILE, *DTAARA, and *DTAQ), default configuration values result in cooperative processing by user journal replication and require the use of data group object entries. When a data group uses journal-centric configuration for these object types, user journal replication is used and data group object entries are only needed to provide additional qualifying information and for excluding objects from replication. User journal replication also requires file entries for *FILE objects and object tracking entries for *DTAARA and *DTAQ objects. A journal-centric data group will automatically create the needed file entries and object tracking entries. See:
When you configure MIMIX, you can create data group object entries by adding individual object entries or by using the custom load function for library-based objects.
Simplifying creation of entries: The custom load function can simplify creating data group entries. This function generates a list of objects that match your specified criteria, from which you can selectively create data group object entries. For example, if you want to replicate all but a few of the data areas in a specific library, you could use the Add Data Group Object Entry (ADDDGOBJE) command to create a single data group object entry that includes all data areas in the library. Then, using the same object selection criteria with the custom load function, you can select from a list of data areas in the library to create exclude entries for the objects you do not want replicated.
Tailoring entries: Once you have created data group object entries, you can tailor them to meet your requirements. You can also use the #DGFE audit or the Check Data Group File Entries (CHKDGFE) command to ensure that the correct file entries exist for the object entries configured for the specified data group.