Working with remote journal error messages
Several different error conditions can occur when the remote journal function is active.
When an error condition is encountered, the system automatically ends the remote journal function on the source system to that remote journal. The system notifies you that a failure occurred. Failure notification is made on both the source system and the target system. Notification is made by sending a message to the journal message queues associated with the source and target journals as appropriate. If remote journal is to automatically restart then additional messages are sent to the journal message queue to indicate the restarting attempts have started, and to indicate that the final restart attempt was not successful.
For help determining why remote journaling ended,
see IBM® Redbooks® technote Journaling - Common Remote Journal
Questions
Additional messages can be sent to the journal message queue for normal remote journal processing. For example, if you requested a controlled inactivate of the remote journal, a message will be sent to the message queue when the inactivate processing has completed.
Even though the remote journal function has been ended, the local journal is not automatically inactivated. Therefore the local system journal entry deposits will continue normally.
The remote journal function messages that are sent to the journal message queue are listed as follows:
- CPI7012
- Recovery procedures for messages CPF70D4 and CPF70D5.
- CPI7016
- Recovery procedures for messages CPF70C4 and CPF70C5.
- CPI7027
- An attempt to restart remote journaling failed, another will be attempted.
- CPI7028
- Remote journaling could not be restarted because either an unrecoverable error was encountered, or the maximum restart attempts were made.
- CPI7031
- Additional recovery procedures for messages CPF70D4 and CPF70D5.
- CPExxxx
- When remote journaling ends due to communication errors, the communication messages are also sent to the journal message queue. These messages will help address communication related problems.
- CPF70C4
- The data port services remote journal function is no longer active due to various reasons. For a synchronously maintained remote journal, there may be unconfirmed entries which may need to be processed prior to the remote journal being inactivated.
- CPF70C5
- The data port services remote journal function is no longer active and has been ended due to various reasons. There are no unconfirmed entries.
- CPF70D3
- A controlled inactivate of a remote journal has completed.
- CPF70D4
- The remote journal function is no longer active due to various reasons. For a synchronously maintained remote journal, there may be unconfirmed entries which may need to be processed prior to the remote journal being inactivated.
- CPF70D5
- The remote journal function is no longer active and has been ended due to various reasons. There are no unconfirmed entries.
- CPF70D6
- The remote journal function was ended due to storage constraints.
- CPF70D7
- There was a problem on the target system while attempting to execute a change journal.
- CPF70DB
- A severe error has occurred with the remote journal function, and service must be notified.
- CPF70DC
- There was a timeout on the target system while attempting to attach a new journal receiver to the remote journal.
Display the messages on your system for more information.