When you end replication of journal entries to a remote journal, it is recommended that the replication of entries be ended from the source system whenever possible, rather than from the target system. Usually, ending replication from the target system for a remote journal is only necessary when the source system has failed, and the system has not ended the remote journal function.
If you are inactivating an asynchronously maintained remote journal, you can request that the remote journal function be ended immediately or in a controlled fashion. For an immediate end, any journal entries which have already been queued for replication will not be sent to the remote journal. For a controlled end, any journal entries which have already been queued for replication will be sent to the remote journal. When all queued entries have been sent to the target system, the system sends message CPF70D3 to the journal message queue. The message indicates that the remote journal function has been ended. If you are inactivating a synchronously maintained journal, the remote journal function is ended immediately, regardless of whether an immediate or controlled end was requested. Similarly, if the remote journal is in the catch-up phase of processing, the remote journal function is ended immediately. This is also regardless of whether an immediate or controlled end was requested.
To inactivate the replication of journal entries proceed as follows:
You can also use the Change Journal State (QjoChangeJournalState) API and Change Remote Journal (CHGRMTJRN) command to inactivate the replication of journal entries to a remote journal. For this purpose, the API can be initiated from either the source system or the target system. The CHGRMTJRN command can only be initiated from the source system. You can also use the Change Journal (CHGJRN) command on the target system to inactivate the remote journal.