FDR V54L78 - Innovation Data Processing

MESSAGES AND CODES
MESSAGES FROM FDR, DSF, AND ABR (FDRNNN) 100.3
D –
E –
F –
G –
H –
J –
K –
L –
M –
N –
Q –
R –
T –
U –
V –
For an ABR restore from volume backups, ABR identified a specific backup
containing the requested data set, but that backup was not cataloged in the
ABR catalog. The backup may have expired or was part of an older
generation that ABR has uncataloged. If COPY=n was specified, it may be
that the specified copy was not created. If the backup file still exists but has
been uncataloged, TAPEDD= can be used to restore the data set.
For an ABR restore from archive backups, the backup file containing the
data set has reached its expiration date (as recorded in the Archive Control
File). If the backup file still exists, you can restore the data set by specifying
TAPE=EXP on the RESTORE control statement.
For an ABR restore from volume backups, the volume from which the data
set was backed up, as specified by the VOL= operand or the catalog, is not
currently initialized for ABR processing; or an I/O error occurred when
reading the ABR Model DSCB controlling the disk volume. If you can
identify an ABR backup that contains the data set, you can specify GEN=,
CYCLE=, and VOL= to restore it.
SELECT statement for a data set restore did not specify VOL=. This data
set was not found in the system catalog, or in ABR's record of scratched
data sets. See reason “B” for suggestions.
The volume from which the data set was backed up, as specified by the
VOL= operand or the system catalog, was not mounted so ABR could not
locate the backup of the data set. If possible, mount the volume. If you can
identify an ABR backup that contains the data set, you can specify GEN=,
CYCLE=, and VOL= to restore it.
GEN= was specified without CYCLE=.
TAPEDD=x was specified but no TAPEx DD was found, or TAPEDD was
specified with TYPE=ARC.
The most likely causes are:
– The data set was not found on the volume specified by the VOL=
operand (if coded) or by the catalog or it was found but had no
current ABR backup recorded in its DSCB.
– The data set was found in the ABR SCRATCH catalog, but with a
different volume serial. This probably occurred because the data
set was scratched and reallocated on a different volume.
– The data set was found in the ABR SCRATCH catalog but the
generation number was invalid.
You can restore the data set by specifying VOL= the volume in the ABR
SCRATCH catalog, or by specifying VOL= and CYCLE= (and possibly
GEN=) for any volume and cycle on which the data set was backed up, or
by specifying TAPEDD=.
COPY=2 was requested for this data set, but the ARCHIVE control data set
indicates that a second copy was not created during archival.
The backup file containing this data set failed to OPEN, or dynamic
allocation error. Check the job log and SYSPRINT for IBM or FDR error
messages. The backup data set may have been written over.
RACF authorization error.
The backup file containing this data set was not an FDR-formatted backup;
or an I/O error occurred reading the FDR Header Record.
A TYPE=ABR restore had a SELECT statement that specified DSG= or
ALLDSN without either TAPEDD= or VOL=, GEN=, and CYCLE=.
DYNTAPE was specified but one or more TAPEx DD statements were also
provided. DYNTAPE attempted to allocate a tape volume already allocated by one
of the TAPEx DDs. Remove the TAPEx DDs and let DYNTAPE allocate all tapes.
For a restore from Archive Backup or Application Backup, the backup file
exceeded 5 tape volumes, but ABR was not able to find an entry for it in the
catalog. The catalog contains the complete volume list, while the Control
File only records the first 5.
CHAPTER 100 – PAGE 100-66 –