Explanation
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.
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:
- Logs were specified in the wrong order in the ALLOCATE statement, 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 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
System action
CICS VR stops the recovery and prints the
reports.
User response
- 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:
SEQCHKR OUTOFSEQUENCE(WARNING)
SEQCHKR 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 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.