DWW0453S

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

Two label records are not in the correct time sequence in log dddd. Record nn2, which precedes record nn1 on the log, has a later time stamp. Also, the sequence numbers of these records are not in sequence.

Note: For CICS® logs, the label sequence numbers nn1 and nn2 are artificially created when CICS® VR converts the label record to CICS/ESA® 4.1 format. So the label sequence numbers do not appear on the native CICS® log.

Some possible causes for this message are:
  • A log has been 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 contained 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 recovery and prints the reports.

  • Batch–Find out why there is a gap in the label records. (Check the contents of the log to see whether all records needed for recovery are present.) 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.