DWW0553S

Record nn1 is found out of sequence when reading backward on log dddd. The preceding record is nn2. Processing terminates.

Two label records are not in the correct time sequence in log dddd. Record nn1, which precedes record nn2 on the log, has a later time stamp. Also, the sequence numbers of these records are not in sequence. Some possible causes for this message are:
  • Logs were archived in the wrong time sequence, or a log was archived twice in a row.
  • A log was written over an older log, and the data set is not closed. This can occur when the system abends.
  • The time and date were specified incorrectly during an IPL of the operating system.
  • A log had data other than log records.
This message is issued if you specified:
  • The SEQCHKR OUTOFSEQUENCE(STOP) command.
  • STOP in the sequence checking secondary window.
  • No option in the out of sequence field of the sequence checking secondary window.

CICS® VR stops the backout and prints the reports.

  • Batch–If logs are specified in the wrong order, contact your local IBM® Support Center.

    If a log was not closed, close it and rerun CICS® VR.

    If you want to accept the error message and run CICS® VR, specify either of these commands:

    SEQCHKR OUTOFSEQUENCE(WARNING)    
    SEQCHKR OUTOFSEQUENCE(IGNORE)

    Remember to restore the VSAM data sets from the backup copies before you rerun CICS® VR.

  • Online–If logs are specified in the wrong order, correct the order and rerun CICS® VR.

    If a log was not closed, close it and rerun CICS® VR.

    If you want to accept the error message and run CICS® VR, specify either WARNING or IGNORE in the sequence checking secondary window.

    Remember to restore the VSAM data sets from the backup copies before you resubmit the recovery job.