DWW0559S

A record is found out of sequence when switching logs and reading backward. Record nn2 on log dddd2 precedes record nn1 on log dddd1. Processing terminates.

Two label records are not in the correct time sequence. Record nn1, which is the last record on log dddd1, has a later time stamp than record nn2, which is the first record on log dddd2. Also, the sequence numbers of these records are not in sequence. Some possible causes for this message are:
  • The logs are specified in the wrong order, or the same log was specified twice.
  • 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 SEQCHKL 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, 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 of these commands:

    SEQCHKL OUTOFSEQUENCE(WARNING)    
    SEQCHKL OUTOFSEQUENCE(IGNORE)

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

  • Online–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 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.