Explanation
A label record with a zero sequence number was
found, and the record before it (
nn1) does not have the
maximum sequence number (2
32-1). Record
nn1
is the last record on log
dddd1, and the zero record is
the first record on log
dddd2. Some possible causes for
this message are:
- The sequence number was reset to zero by CICS®. If you do not have a journal archive
control data set (JACD), CICS resets
the sequence number at every cold start and warm start. CICS VR functions
correctly in this situation.
- A log was omitted when specifying the logs in the ALLOCATE statement,
and the next log started with a zero record.
- A zero sequence number occurred because the JACD is damaged or lost. CICS VR
functions correctly in this situation.
- A log was skipped during archiving, and the next log started with a record
with a zero sequence number.
- A log contained data other than log records.
This message is issued if command SEQCHKL
RESETSEQUENCE(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 the sequence number was reset to zero because you are
not using a JACD, no action is required.
If you omitted a log, archive this
log and rerun CICS VR.
If
you are using a JACD, find out why the zero sequence number occurred. If the
JACD is damaged or lost, no action is required. If a log was skipped during
archiving, rerun CICS VR after archiving the log. In other cases, 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 the sequence number was reset to zero because you are
not using a JACD, no action is required.
If you omitted a log, archive this
log and rerun CICS VR.
If
you are using a JACD, find out why the zero sequence number occurred. If the
JACD is damaged or lost, no action is required. If a log was skipped during
archiving, rerun CICS VR after archiving the log. In other cases, 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.