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 logs 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 command SEQCHKL
GAPINSEQUENCE(WARNING) is specified, or if WARNING is specified in the sequence
checking secondary window.
System action
CICS VR continues the recovery.
User response
- Batch–If you omitted a log that does not contain any records
needed for the recovery run, no action is required. CICS VR recovery functions correctly when
a log is missing if the log does not contain any records for the data sets
being recovered.
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.)
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, no action is required. CICS VR recovery functions correctly when
a log is missing if the log does not contain any records for the data sets
being recovered.
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.)
Remember
to restore the VSAM data sets from the backup copies before you resubmit the
recovery job.