A gap is encountered when switching logs and reading forward.
Record nn1 on log dddd1 precedes record nn2
on log dddd2. Processing terminates.
Explanation
A sequence number gap was found between two label
records when switching logs; the sequence numbers are not in sequence. The
records are in the correct time sequence. That is, record
nn1,
which is the last record on log
dddd1, has an earlier time
stamp than record
nn2, which is the first record on log
dddd2.
This message might mean that records needed for recovery are missing. Some
possible causes are:
- A log was omitted when specifying the log to CICS® VR in the ALLOCATE statement, or logs
are specified in the wrong order.
- A log was skipped during archiving.
- Label records were skipped over by a selective archiving program; records
needed for recovery 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 contained 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 recovery and prints the
reports.
User response
- Batch–If you omitted a log that does not contain any records
needed for the recovery run, the run will be successful if you rerun CICS VR and specify
either of these commands:
SEQCHKR GAPINSEQUENCE(WARNING)
SEQCHKR GAPINSEQUENCE(IGNORE)
If a log containing records
needed for recovery is 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 recovery 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 you omitted a log that does not contain any records
needed for the recovery run, the run will be successful if you rerun CICS VR and specify
either WARNING or IGNORE in the sequence checking secondary window.
If
a log containing records needed for recovery is 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 recovery 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.