Effect of changes to an object’s journaling - 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

In a journal-centric data group, the journaling status of the objects determines whether transactions for the objects can be replicated. Ending journaling for an object, or changing its journaling to a different journal, removes the object from the replication name space and ends its ability to be replicated.

Changes to an object’s journaling that moves the object from the name space of one data group to the name space of another data group are detected and potential problems are corrected. When the new data group for the journaled object is processing journal entries from a more recent point in the journal, the status of the object’s File Activity, IFS Tracking Activity, or Object Tracking Activity entry is set to Held Retry (*HLDRTY) until the original data group processes the journal entry indicating that journaling was ended for the object.

Manually starting or ending journaling: For journaled objects identified by file activity entries, Object tracking activity entries, and IFS tracking activity entries, Precisely recommends using MIMIX commands to start and end journaling for the files, objects, and IFS objects defined to a data group. As long as an activity entry exists for the object on which you need to end or start journaling, you can use these MIMIX commands to do so: ENDJRNFE and STRJRNFE for files, ENDJRNOBJE and STRJRNOBJE for data areas, data queues, or libraries, and ENDJRNIFSE and STRJRNIFSE for IFS objects. By using the MIMIX commands, you ensure that MIMIX processing is aware of the status of journaling and that the file is journaled to the configured journal.

In a journal-centric data group when an activity entry or tracking entry does not exist, before MIMIX can create it and identify a file or object as eligible for replication, you must journal the file, data area, data queue, or IFS object to the journal associated with the data group using these IBM commands: STRJRNPF for files, STRJRNOBJ for data areas and data queues, STRJRNLIB for libraries, and STRJRN for IFS objects.