FDR V54L78 - Innovation Data Processing

MESSAGES AND CODES
MESSAGES FROM FDR, DSF, AND ABR (FDRNNN) 100.3
For a VSAM component, the line containing “cluster” is displayed to identify the cluster
to which the component belongs. If the cluster is being restored to a new name,
“newcluster” is the cluster's new name.
FDR312 WARNING--FDR WAS SPECIFIED WITH DSNAME CONTROL STATEMENTS--
STATEMENTS IGNORED
Reason: SELECT statements were found following an ABR DUMP TYPE=FDR command. They are
ignored and all data sets on the volume are backed up. However, If EXCLUDE ALLDSN
control statements are found, the volumes specified are EXCLUDED from the full-volume
dump if they are not referenced by DISKxxxx DD statements.
FDR313 fff TERMINATED BY OPEN EXIT ON VOL= vvvvvv
Reason: The locally-written FDR volume open exit has terminated processing of the volume
“vvvvvv”. “fff” is FDR, ABR, or CPK.
FDR314 program status1 dsn [status2]
Reason: For an ABR Archive Backup or Superscratch (“program” is ABR), or an ABR Application
Backup (APP) or an FDRCOPY MOVE (FDR), this documents the action taken on one
non-VSAM data set, VSAM component, or VSAM cluster. It can also be produced on
any type of restore if RECAT or VRECAT is specified.
“dsn” is:
DSNAME=dsn – For a non-VSAM data set.
CLUSNM=cluster – For a VSAM cluster.
VSAM COMP=component – For a component of a VSAM cluster.
“status1” can be:
ARCHIVED AND SCRATCHED – Archive Backup backed up and scratched the data set.
ARCHIVED NO SCRTCH – Archive Backup backed up the data set but it was not
scratched because SCRATCH=NO was specified.
ARCHIVE DEFER SCRATCH – Archive Backup backed up components of a multivolume
cluster from one volume but deletion of the cluster is deferred until
all volumes containing the cluster have been processed (they must all be
processed in the same ABR step).
WITH NO BACKUP – Superscratch deleted the data set.
APPLICATION BACKUP OF – Application Backup backed up this data set.
SCRATCHED – An FDRCOPY MOVE scratched the input data set after copying it
to the output. Can also occur when VRECAT causes an existing VSAM
cluster to be deleted.
UNCATALOGED – An FDRCOPY MOVE or restore with RECAT caused an
existing SMS-Managed data set to be uncataloged.
“status2” can be blank or one of these:
AND UNCATALOGED – Archive Backup, Superscratch or MOVE also uncataloged
the scratched data set.
AND UNCATALOGED RECAT FAILED – A VSAM cluster was archived with
RECALL=YES and the attempt to catalog it as a non-VSAM data set for
auto-recall failed, leaving it uncataloged. It cannot be auto-recalled.
RECAT FOR RECALL – A data set was archived with RECALL=YES. The catalog
entry has been updated to indicate that the data set is auto-recallable.
RECAT FOR RECALL FAILED – A non-VSAM data set was archived with
RECALL=YES but an error occurred attempting to re-catalog the data set
for auto-recall. The data set is still cataloged but is not auto-recallable.
Action: If the status includes RECALL FAILED or RECAT FAILED, the indicated data set is not
auto-recallable. If you can delete any existing catalog entry for the data set, you may be
able to use the RECATALOG function of FDRARCH (Section 51.50 “Archive Maintenance
Utility (FDRARCH)”) to build the auto-recall catalog entry.
CHAPTER 100 – PAGE 100-61 –