Requirements and limitations of legacy cooperative processing - 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

Legacy cooperative processing requires that data groups be configured for both database (user journal) and object (system journal) replication and that the data group specifies *SYSJRN for Cooperative journal (COOPJRN). While remote journaling is recommended, MIMIX source-send processing for database replication is also supported. Specific data group definition and data group entry requirements are listed in Table 16.

Legacy cooperative processing configurations have the following limitations.

Supported extended attributes - Legacy cooperative processing supports only data files (PF-DTA and PF38-DTA).   

When a *FILE object is configured for legacy cooperative processing, only file and member attribute changes identified by T-ZC journal entries with access types of access types of 7 (Change), 62 (Add constraint), 63 (Change constraint), and 64 (Remove constraint) are logged and replicated through system journal replication processes. All member and data changes are logged and replicated through user journal replication processes.

File entry options - If a file is moved or renamed and both names are defined by a data group file entry, the file entry options must be the same in both data group file entries.

Referential constraints - Physical files with referential constraints require a field in another physical file to be valid. All physical files in a referential constraint structure must be in the same apply session. If this is not possible, contact Support.