An unexpected zero sequence number is found when reading
backward on log dddd. The zero record precedes record nn1.
Processing terminates.
Explanation
A label record with a zero sequence number was
found, and the record before it on the log (
nn1) does not
have the maximum sequence number (2
32-1). Both records are on log
dddd.
Some possible causes for this message are:
- The sequence number was reset to zero by CICS®. If you are not using 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 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 had 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 reset sequence field of the sequence checking secondary window
System action
CICS VR stops the backout and prints the
reports.
User response
- Batch–If the sequence number was reset to zero because you are
not using a JACD, specify either of these commands: SEQCHKR RESETSEQUENCE(WARNING)
SEQCHKR RESETSEQUENCE(IGNORE) Then restore a new copy from the backup 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 backout are
present.
If you want to accept the error message and run CICS VR, specify
either of these commands:
SEQCHKR RESETSEQUENCE(WARNING)
SEQCHKR RESETSEQUENCE(IGNORE)
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, specify either WARNING or IGNORE in the sequence checking
secondary window. Then restore a new copy from the backup 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 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.