FDR V54L78 - Innovation Data Processing

MESSAGES AND CODES
MESSAGES FROM FDR, DSF, AND ABR (FDRNNN) 100.3
Action:
S –
T –
U –
V –
W –
X –
Y –
Z –
– PDSE to non-PDSE
– HFS to non-HFS
– Extended Format SMS to non-EF
– And vice-versa in each case. Other combinations also cause errors.
A data set that must be SMS-Managed (such as Extended Format (EF)) is
being restored to a non-SMS volume.
FDRCOPY COPY/MOVE detected a copy/move of a data set on top of itself
(same volser, same data set name).
Error updating ISAM Format 2 DSCB, or VSAM component in the VTOC but
not in the VVDS.
VSAM cluster is being restored to a VSAM cluster that has different options
or characteristics. Message FDR152 or FDR159 details the error.
Catalog inaccessible. Possible causes are:
– When restoring a catalog, the JCL contained a STEPCAT or
JOBCAT DD statement. This is not supported.
– When restoring a catalog, the catalog being restored was defined
in the master catalog, but it was not usable (probably did not
actually exist on disk). You must remove the entry for the old
catalog, probably by IDCAMS EXPORT DISCONNECT.
Data set security exit rejected this data set
NEWINDEX= failure or duplicate data set name generated. It may be that
the new data set name does not meet IBM standards, or that the resulting
name is greater than 44 characters.
One or more data sets failed to restore using ALLDSN or DSN=mask.
Check the subtask listing for errors.
Take appropriate action and/or contact INNOVATION DATA PROCESSING for assistance.
FDR321 UNABLE TO RESTORE REASON=x--DSNAME=dsname
Reason: The data set specified in the message could not be restored. The reason code “x” may be:
2 – The ABR JCL does not include any DISKxxxx DD statement pointing to a disk
volume of the same type (e.g., 3390) as the original volume of the data set.
3 – The OPERATOR operand was specified, but the operator replied “NO” or
“BYPASS” to the request for the backup tapes needed to restore the data set.
5 – The disk volume that FDR was attempting to restore the data set could not
be opened, or could not be dynamically allocated.
A – For an ABR restore from volume backups, the data set was found on disk and
ABR is trying to get backup information from its DSCB, but no current backup
information was recorded. Either the data set has never been backed up by
ABR or it has been deleted and reallocated since its last backup. This can also
occur if some other software has corrupted ABR's backup information in the
DSCB. If you can identify an ABR backup that contains the data set, you can
specify GEN=, CYCLE=, and VOL= to restore it.
B – For an ABR restore from volume backups:
– The data set is not cataloged and VOL= was not specified.
– The data set is not on the volume identified by the system catalog
(or by the VOL= operand).
– It was also not found in ABR's record of scratched and renamed data
sets (the ABR SCRATCH catalog). The most likely causes are:
– The DSN= or VOL= operand is incorrect.
– The data set was archived.
– ABR is not recording scratched and renamed data sets (ABR
DADSM exit not installed).
If you can identify an ABR backup that contains the data set, you can
specify GEN=, CYCLE=, and VOL= to restore it.
CHAPTER 100 – PAGE 100-65 –