Tweet
We received this message in one of our servers the other day. I am not sure what to do about it. The message type is Information. Here is the full message:
Message . . . . : Journal recovery may not be complete.
Cause . . . . . : An error occurred while trying to determine or access one or more journals or journal receivers during journal IPL recovery part 1.
During part 1 recovery, the most likely cause is that one or more journals or journal receivers are damaged.
During part 2 recovery, the most likely cause is that there was a lock conflict on a journal or journal receiver or we were unable to enqueue an
operation to a server job.
Recovery . . . : Use the Display Job Log (DSPJOBLOG) command to display the SCPF job log that contains this message. Zero or more messages pertaining
to journal recovery will appear just prior to this message. If a journal or journal receiver is damaged, then delete the object and restore a previously saved version.
If there was a lock conflict on a journal or journal receiver, use the Work with Journal Attributes (WRKJRNA) command to determine if the journal
had the MNGRCV(*SYSTEM) attribute. If so, then try to delete all detached journal receivers in the journal's receiver directory. If you receive a
CPF7024 message (journal receiver in use), CPF70ED message with reason code 1, (exit program prevents delete) or CPF705F message (receiver not
completely replicated), the system will delete the receiver when it is no longer needed. If the journal does not have the MNGRCV(*SYSTEM) attribute,
then ignore this message.
If no damaged objects were found, and there were no lock conflicts, then report the problem (ANZPRB).
The message was received after a journal was detached because the journal had MNGRCV(*SYSTEM) and it is not damaged. How do I delete the detached journal receivers?
Message . . . . : Journal recovery may not be complete.
Cause . . . . . : An error occurred while trying to determine or access one or more journals or journal receivers during journal IPL recovery part 1.
During part 1 recovery, the most likely cause is that one or more journals or journal receivers are damaged.
During part 2 recovery, the most likely cause is that there was a lock conflict on a journal or journal receiver or we were unable to enqueue an
operation to a server job.
Recovery . . . : Use the Display Job Log (DSPJOBLOG) command to display the SCPF job log that contains this message. Zero or more messages pertaining
to journal recovery will appear just prior to this message. If a journal or journal receiver is damaged, then delete the object and restore a previously saved version.
If there was a lock conflict on a journal or journal receiver, use the Work with Journal Attributes (WRKJRNA) command to determine if the journal
had the MNGRCV(*SYSTEM) attribute. If so, then try to delete all detached journal receivers in the journal's receiver directory. If you receive a
CPF7024 message (journal receiver in use), CPF70ED message with reason code 1, (exit program prevents delete) or CPF705F message (receiver not
completely replicated), the system will delete the receiver when it is no longer needed. If the journal does not have the MNGRCV(*SYSTEM) attribute,
then ignore this message.
If no damaged objects were found, and there were no lock conflicts, then report the problem (ANZPRB).
The message was received after a journal was detached because the journal had MNGRCV(*SYSTEM) and it is not damaged. How do I delete the detached journal receivers?