Deactivating a remote journal using iSeries Navigator
When you deactivate a remote journal, the collection of data is stopped. If you are deactivating a synchronously maintained journal, the remote journal function is ended immediately, regardless of whether an immediate or controlled end is requested. If the remote journal is in the catch-up phase of processing, the remote journal function is ended immediately, regardless of whether an immediate or controlled end is requested. (Catch-up processing refers to the process of replicating journal entries that existed in the journal receivers of the source journal before the remote journal was activated.) Remote journals are in catch-up if they have a delivery mode of asynchronous pending or synchronous pending.
- Controlled
- Deactivates the remote journal function in a controlled manner. This means that the system should replicate all journal entries already queued to be sent from the source system to the target system before deactivating the remote journal. Until all queued entries have been replicated, the remote journal will be in a state of inactive pending. While in a state of inactive pending, the Remote Journals window provides inactive pending information. When all queued entries have been sent to the target system, the system sends a message to the journal message queue, indicating that the remote journal function has been ended.
- Immediately
- Deactivates the remote journal function immediately. This means that the system should not continue to replicate any journal entries that are already queued before deactivating the remote journal.
Parent topic:
Working with journals