FDR V54L78 - Innovation Data Processing

FDR020
Reason:
Action:
MESSAGES AND CODES
MESSAGES FROM FDR, DSF, AND ABR (FDRNNN) 100.3
RACF VOLUME PROTECTION FAILED ON VOL=vvvvvv
Security checking was enabled in the FDR Global Options Table. A full volume dump or restore
was requested but a security call for class DASDVOL and volume “vvvvvv” failed. The user
does not have sufficient authority to perform this operation. This message is produced only for
full-volume restores and absolute track operations; full-volume backups and data set operations
do class DATASET checks against individual data sets if the DASDVOL check fails.
An U0801 ABEND is issued.
FDR021 RACF DATA SET PROTECTION FAILED ON DSN=dsname
Reason: Security checking was enabled in the FDR Global Options Table. A security call for
class DATASET and data set name “dsname” failed. The user did not have sufficient
authority to access this data set.
Action: On a full volume backup operation, the backup is terminated. On a data set operation,
this data set is bypassed.
FDR022 RESTORE TAPE IS A DSF FORMATTED TAPE
Reason: A full volume restore was requested from a backup created by an FDRDSF or FDRABR
data set backup. This backup may not contain an image of the entire volume.
Action: Normally FDR terminates the RESTORE with an U0205 ABEND. If TAPE=DSF was coded
on the RESTORE control statement, FDR continues the RESTORE. Warning messages
are issued if the volume LABEL or VTOC are not found on the tape.
FDR023 DUMMY VTOC READ -- ENTIRE PACK WILL BE DUMPED
Reason: FDR found that the VTOC on this volume started and ended on cylinder zero head zero.
This is the format used on volumes initialized by VM; that dummy VTOC is not valid.
Action: FDR dumps all tracks on the volume.
LINUX VOLUME VOL=volser
Reason: This form of the FDR023 message indicates that FDR identified the volume as one that
was formatted by Linux for the S/390 or System z system. The volume is in Linux
Compatible Disk Layout (CDL) format with a VTOC in a special format.
Action:
FDR processes the Linux partitions that are identified by DSCBs in the Linux CDL VTOC.
FDR024 INVALID EXTENT DESCRIPTOR [REASON=reason DSN=dsname]
Reason: FDR read a DSCB (Format 1 or 3) that contained an invalid extent description. If a mini
dump is printed, the first five bytes of the DSCB printed after the registers in the
mini-dump are the cylinder, head, and record number (CCHHR) of the DSCB in error.
If REASON= is printed, it is one of the following:
1 – ENDING CYLINDER TOO LARGE
2 – STARTING TRACK TOO LARGE
3 – ENDING CCHH BEFORE BEGIN
4 – ENDING TRACK TOO LARGE
NOTE: Reasons “2” and “4” indicate that the starting or ending track number of an extent
is higher than the highest track on a cylinder, i.e., higher than 14 on 3380 or 3390;
not that the start or end of an extent is after the end of the pack.
Action:
Depending on the operation, FDR may continue the backup and dump all tracks on the
volume, or may terminate with an U0110 ABEND.
Scratch the bad data set.
If an absolute track statement was specified (SELECT FROM/TO), the user specified a
cylinder address greater than maximum cylinder number or a track number greater
than the tracks per cylinder. Correct the SELECT statement.
If necessary, contact INNOVATION DATA PROCESSING for assistance.
CHAPTER 100 – PAGE 100-19 –