A gap is encountered between record nn1
and record nn2 on log dddd when reading
backward. Processing terminates.
Explanation
A sequence number gap was found between two label
records in log
dddd; the sequence numbers are not in sequence.
The records are in the correct time sequence. That is, record
nn2,
which precedes record
nn1 on the log, has an earlier time
stamp. This message probably means that records needed for backout are missing.
Some possible causes are:
- A log was skipped during archiving.
- Label records were skipped over by a selective archiving program; records
needed for backout might also be skipped.
- The journal archive control data set (JACD)
is damaged or inaccessible, causing the wrong sequence numbers to be used
on label records.
- A log had data other than log records.
This message is issued if you specified:
- The SEQCHKR GAPINSEQUENCE(STOP) command
- STOP in the sequence checking secondary window
- No option in the gap in sequence field of the sequence checking secondary window
System action
CICS® VR stops the backout and prints the
reports.
User response
- Batch–If a log was missing, archive this log and rerun CICS VR.
If
all logs are present, find out why there is a gap in the label records. (Check
the contents of the log to see whether all records needed for backout are
present.)
If you want to accept the error message and run CICS VR, specify
either of these commands:
SEQCHKR GAPINSEQUENCE(WARNING)
SEQCHKR GAPINSEQUENCE(IGNORE)
Remember to restore the
VSAM data sets from the backup copies before you rerun CICS VR.
- Online–If a log was missing, archive this log and rerun CICS VR.
If
all logs are present, find out why there is a gap in the label records. (Check
the contents of the log to see whether all records needed for backout are
present.)
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.