A description of the information that is provided in the
recovered data statistical report.
Base name of recovered, or backed out, data set
The VSAM base cluster that CICS® VR
allocates and updates.
Base name of original data set
The data set name that CICS® used when it accessed the
VSAM base cluster.
Paths that are defined in the VSAM catalog
Path names that are found in the VSAM catalog entry
for the recovered data set. You can check these
path names to confirm that the entire sphere existed during the CICS® VR
run.
First and last records applied
The time-stamp of the first and last after-image, or before-image,
that was applied to the VSAM data set. The date is taken from a label
record, and the time is taken from the after-image or before-image.
Time type identifies the time format, GMT or LOCAL, of the applied
records.
Name of recovered data set
The VSAM component name of the recovered data set. This data set
can be a base cluster or path. If you used the NEWSPHERE keyword in
the CICS® VR run, the name of this field is Original
name of recovered data set. This field shows the original
VSAM component name that was found on the log.
Data set type
Base or path.
FCT entry name
The CICS® file control table (FCT) entry names for
this VSAM sphere that were used during the period that is covered
by the logs.
Number of records (or Records found on the log)
For each file, the total number of records that are
found on the logs that relate to the file.
If the CICS® VR
run ends with an error message, these statistics will not match the
number of records that are shown in the MVS™ log
stream, log data set, or journal data set statistics report.
Number of changed records (or Change records applied)
The amount of times CICS® VR added, updated, or deleted
a record in the VSAM data set within the specified, or default, START/STOP
times.
Changes that are ignored by exit
The number of after-images or before-images that were ignored
in the preapply exit.
** Failures **
The number of failures because of duplicate or not found conditions.
This field might be in the report of a forward recovery that ran using CICS® logs.
It can also be in the report of a forward recovery run that used data
sets that were backed up using BWO.
Corresponding messages in
the ranges DWW0601 - DWW0605 and DWW0621 - DWW0627 might also be produced
in the DWWMSG file. If the data set being recovered was backed up
with the backup-while-open facility, message DWW0635 is displayed.
For information about acceptable VSAM errors, see the error exit description
in CICS® VR Implementation Guide and Reference.
The following figure is an excerpt from a recovered data set statistics
report and shows the format of the Failures section.
Figure 1. Recovered
data set statistics report – Failures section
DATASET FCT ENTRY IGNORED
TYPE NAME DSNAME UPD-AFTER ADD-AFTER DEL-AFTER ADDS UPDATES DELETES BY EXIT
------- --------- ------ --------- --------- --------- ---- ------- ------- -------
BASE MAIN 1 1 3 1 0 0 0 0
Records due to CICS backout: 0 0 0 0 0 0 0
CHANGED CHANGED IGNORED
0 0 0
------- --------- ------ --------- --------- --------- ---- ------- ------- -------
TOTAL 1 1 3 1 0 0 0 0
Records due to CICS backout: 0 0 0 0 0 0 0
CHANGED CHANGED IGNORED
0 0 0
------- --------- ------ --------- --------- --------- ---- ------- ------- -------
** FAILURES ** DUE TO DUPLICATE OR NOT FOUND CONDITIONS: ADDS = 3 UPDATES = 1 DELETES = 1
Records due to CICS backout: 0 0 0
CHANGED = 0 CHANGED = 0 IGNORED = 0
A failure can occur for the following reasons:
Adds
When the access key from a CICS® log
record does not match the key in the log record, (see message DWW0627)
When acceptable errors are met, as detailed in the description
of the error exit in Error exit: pass I/O error informationCICS® VR Implementation Guide and Reference.
For example, when a data set is recovered using a BWO backup, an attempt
to add a record might fail because the record is already present,
in which case, the operation is changed to update the record instead.
Updates
When the access key from a CICS® log
record does not match the key in the log record (see message DWW0627)
If a path update from a CICS® log attempts to change the
base key (see message DWW0626)
If a non-unique key is encountered for a CICS® log
during a path update or delete (see message DWW0625)
When acceptable errors are met, as detailed in the description
of the error exit in Error exit: pass I/O error informationCICS® VR Implementation Guide and Reference.
For example, when a data set is recovered using a BWO backup, an attempt
to update a record might fail because the record is not present, in
which case, the operation is changed to add the record instead.
Deletes
If a non-unique key is encountered for a CICS® log
during a path update or delete (see message DWW0625)
When acceptable errors are met, as detailed in the description
of the error exit in Error exit: pass I/O error informationCICS® VR Implementation Guide and Reference.
For example, when a data set is recovered using a BWO backup, an attempt
to delete a record might fail because the record is already not present,
in which case, the delete is ignored.
Note:
The ** Failures ** field
is not illustrated in the example (Report of recovered data sets statistics),
because failures are shown only in the circumstances that are mentioned
earlier.