Identifying logical and physical files for replication - 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

MIMIX supports multiple ways of replicating *FILE objects with extended attributes of LF, PF-DTA, PF38-DTA, PF-SRC, PF38-SRC. MIMIX configuration data determines the replication method used for these logical and physical files. The value specified for the Cooperative journal (COOPJRN) parameter in the data group definition determines whether files will be processed primarily through the user journal or the system journal.

The following configurations are possible for replicating logical and physical files:

  • Default cooperative processing for files - Shipped defaults for configuration commands result in this strongly recommended configuration. In this configuration, logical files and physical files (source and data) are replicated primarily through the user (database) journal. This configuration is the most efficient way to replicate LF, PF-DTA, PF38-DTA, PF-SRC, and PF38-SRC files. In this configuration, the data group specifies to use the user journal for cooperative processing (COOPJRN(*USRJRN)) and files are identified by data group object entries and file entries.

Note: If the data group uses the optional journal-centric configuration for objects of type *FILE, data group object entries are generally not needed to replicate files 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 file selection rules (data group file entries) it needs. When a journal-centric data group is created from the native user interface, you must manually create the data group file entries using the default values on the LODDGFE command.
  • Legacy cooperative processing - Legacy cooperative processing supports only data files (PF-DTA and PF38-DTA). It does not support source physical files or logical files. In legacy cooperative processing, record data and member data operations are replicated through user journal processes, while all other file transactions such as creates, moves, renames, and deletes are replicated through system journal processes. Legacy cooperative processing requires that the data group specify *SYSJRN for cooperative journal (COOPJRN), which is not the shipped default for new data groups. The database processes can use either remote journaling or MIMIX source-send processes, making legacy cooperative processing the recommended choice for physical data files when the remote journaling environment is not possible. In this configuration, files are identified by data group object entries and file entries.

  • User journal (database) only configurations - Environments that do not use remote journaling but which have data group definitions that specify TYPE(*DB) can only replicate data changes to physical files. These configurations may not be able to replicate other operations such as creates, restores, moves, renames, and some copy operations. In this configuration, files are identified by data group file entries.

  • System journal (object) only configurations - Data group definitions which specify TYPE(*OBJ) are less efficient at processing logical and physical files. The entire member is updated with each replicated transaction. Members must be closed in order for replication to occur. In this configuration, files are identified by data group object entries.

Some advanced techniques may require specific configurations. See Configuring advanced replication techniques for additional information.

You should be aware of common characteristics of replicating library-based objects, such when the configured object auditing value is used and how MIMIX interprets data group entries to identify objects eligible for replication. For this information, see Configured object auditing value for data group entries and How MIMIX uses object entries to evaluate journal entries for replication.