Explanation
No updates were applied to VSAM sphere
dddd because no after-images
are found on the log during the specified (or default) start⁄stop times, or
you have specified System Management Facility (SMF) logging journal control
table (JCT). If the data set to be forward recovered was restored from
a backup-while-open (BWO)
dump, then the BWO bits will remain at X'101'. A BWO bit setting
of X'101' indicates that a forward recovery is required.
System action
CICS® VR continues with the recovery run.
User response
- Batch–Check that the JCT does not specify logging in SMF format.
If a start/stop time is specified, check that they are correct. If start/stop
times are omitted, ensure that all logs are supplied in the forward recovery
run. If not, resubmit the CICS VR job with the additional logs.
If there really
are no updates to apply to this data set, set the backup-while-open (BWO)
bits to 000 using the following procedure:
- Select option 1 (List of VSAM spheres) from the CICS VR main menu (panel DWWPPMEN). This
will display the CICS VR VSAM sphere list panel (DWWPPVLT).
- Select data set dddd.
- Using the Tools pull down menu, select option 5 to set the BWO bits to
X'000 for the selected data set.
If the REDO records written by the CICS VR batch logger should be applied
during forward recovery, ensure the RCDS allocated in the recover job is the
same RCDS that was allocated to the CICS VR server address space when the CICS VR
batch logging occurred. Then, rerun the forward recovery job.
If
the REDO records written by the CICS VR batch logger should be applied
during forward recovery, ensure the RCDS allocated in the recover job is the
same RCDS that was allocated to the CICS VR server address space when the CICS VR
batch logging occurred. Then, rerun the forward recovery job.