Automatically restarting remote journal
Remote journaling is dependent on communications networks staying active. But, the reality is that remote journal connections can be dropped for various reasons. To help limit the effect of communications outages, remote journaling has an automatic restart capability. This restart capability is indicated when activating remote journaling.
During the activation of a remote journal connection, you can choose to use the automatic restart capability or not. When you choose to use the automatic restart capability, you specify the number of restart attempts to be made, and the amount of time to wait between each restart attempt.
When remote journaling ends for a recoverable error, a job is started in the QSYSWRK subsystem for the restart attempts. If the first attempt to restart fails, message CPI7027 is sent to QSYSOPR indicating when the next restart attempt will be made. If all restart attempts fail, or one of them fails for an unrecoverable error then message CPI7028 is sent.
These are the recoverable errors that will trigger an automatic restart:
These reason codes for message CPF70D5 (Remote journal environment ended for journal) indicate a recoverable error that will trigger an automatic restart:
- 4 - Communication line error or target system error.
- 5 - Target system error.
- 7 - Storage limit exceeded for system, user or group profile.
- 11 - Time out waiting for a response from the target system.
- 12 - Asynchronous remote journaling could not keep up.
- 21 - Source system could not detect the target system.
- 28 - Communication validity check failed.
- 48 - Data port services error.
- 49 - Node identifier &11 is unavailable for data port services.
- 50 - Connections down for data port services.
- 52 - Destination internet address unreachable for data port services.
- 53 - Hardware error for data port services.
- 54 - Insufficient memory to perform data port services request.
- 55 - Client closed for data port services.