New file processing when default cooperative processing is used - 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

When a data group and its data group object and file entries are properly configured to use default cooperative processing for files, new files created on the source system that are eligible for replication will be created on the target system by MIMIX. The following briefly describes the events that occur for newly created files on the source system that are eligible for cooperative processing through the user journal:

  • System journal replication processes ignore the creation journal entry (T-CO), knowing that user journal replication processes will get a create journal entry (D-CT) as well.

  • User journal replication processes dynamically add a data group file entry when a file create is seen in the user journal. The file entry is added with a status of *ACTIVE.

  • User journal replication processes create the file on the target system. Replication proceeds normally after the file has been created.

  • All subsequent file changes including moves or renames, member operations (adds, changes, and removes), member data updates, file changes, authority changes, and file deletes are replicated through the user journal.

  • In configurations that use single-threaded database apply processing and default cooperative processing for files, MIMIX attempts to place files that are related due to referential constraints into the same apply session. This eliminates the possibility of constraint violations that would otherwise occur if apply sessions processed the files independently. However, there are some situations where constraints are added dynamically between two files already assigned to different apply sessions. In this case, the constraint may need to be disabled to avoid the constraint violations. In the case of cascading constraints, where a modification to one file cascades operations to related files, MIMIX will always attempt to apply the cascading entries, whether the constraint is enabled or disabled, to ensure that the modification is done. In data groups configured to allow target constraint management, MIMIX initially attempts to place newly created files with referential constraints in the same apply session as the referenced file. The next clear pend start of the data group may reassign files that are constrained together to different apply sessions. For more information, see Target constraint management.