Considerations when journaling on target - 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

The default behavior for MIMIX is to have journaling enabled on the target systems for the target files. After a transaction is applied to the target system, MIMIX writes the journal entry to a separate journal on the target system. This journaling on the target system makes it easier and faster to start replication from the backup system following a switch. As part of the switch processing, the journal receiver is changed before the data group is started.

In a remote journaling environment, these additional journal receivers can become stranded on the backup system following a switch. When starting a data group after a switch, the IBM i remote journal function begins transmitting journal entries from the just changed journal receiver. Because the backup system is now temporarily acting as the source system, the remote journal function interprets any earlier receivers as unprocessed source journal receivers and prevents them from being deleted.

To remove these stranded journal receivers, you need to use the IBM command DLTJRNRCV with *IGNTGTRCV specified as the value of the DLTOPT parameter.