FDR V54L78 - Innovation Data Processing
FDR V54L78 - Innovation Data Processing
FDR V54L78 - Innovation Data Processing
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
MESSAGES AND CODES<br />
MESSAGES FROM <strong>FDR</strong>, DSF, AND ABR (<strong>FDR</strong>NNN) 100.3<br />
<strong>FDR</strong>012 NOT AN <strong>FDR</strong> TAPE DSN=dsname<br />
Reason: 1.The input for a restore (“dsname”) is not an <strong>FDR</strong> created backup.<br />
2.The JCL specifies the wrong serial numbers, or specifies the serials in the wrong<br />
order. <strong>FDR</strong> must always read the backup from the beginning; it cannot start in the<br />
middle of a multi-volume backup. If you specified the volume serials of the backup<br />
tape in JCL, check the order of the serials.<br />
3.The <strong>FDR</strong> backup file may have been written over.<br />
Action: “dsname” is the tape data set name. A mini dump is printed displaying the first tape<br />
block read. An U0205 ABEND is issued.<br />
NOTE: The first block of a valid <strong>FDR</strong> backup is a 24 byte record containing the text<br />
“THATS ALL FOLK”. If anything else is displayed, see the reasons above.<br />
<strong>FDR</strong>014 TAPE BACKUP IS INCOMPATIBLE WITH RESTORE DEVICE<br />
Reason: An attempt was made to do a full-volume restore or copy to an unlike device type (e.g.:<br />
3380 to 3390). Use <strong>FDR</strong>DSF, <strong>FDR</strong>COPY, or <strong>FDR</strong>ABR data set restore to restore to a<br />
device with different device geometry. It can also occur when attempting to do a<br />
full-volume restore to a smaller disk of the same type (e.g., 3390-3 to 3390-2).<br />
Action:<br />
The <strong>FDR</strong> header read is printed in a mini dump. An U0104 ABEND follows. If necessary, contact<br />
INNOVATION DATA PROCESSING for assistance. If you want to force <strong>FDR</strong> to restore to a<br />
smaller disk of the same type, specify PROT=NONE on the RESTORE or COPY statement.<br />
The <strong>FDR</strong>014 message is still printed, but the RESTORE or COPY is attempted. You get I/O<br />
errors if any tracks above the capacity of the smaller disk must be restored. If all of the data on<br />
the larger disk fits on the smaller disk, use COMPAKTOR to restore and relocate the data.<br />
<strong>FDR</strong>019 RACF FACILITY PROTECTION FOR BYPASS FAILED FOR resource<br />
Reason: The operands BYPASSACS or BYPASSSMS were specified. To use these, the user<br />
must be authorized to the RACF resource:<br />
STGADMIN.ADR.RESTORE.BYPASSACS (for restore)<br />
STGADMIN.ADR.COPY.BYPASSACS (for copies)<br />
Action:<br />
Reason:<br />
Action:<br />
in class FACILITY or the equivalent in other security systems, but the security check failed.<br />
A control card error is issued and the operation terminates. Authorize the user to the<br />
resource or run the program under a different userid.<br />
RACF FACILITY PROTECTION STGADMIN FAILED FOR resource<br />
In this form of the <strong>FDR</strong>019 message, the operand STGADMIN was specified for<br />
simplified storage administrator security authorization. The user must be authorized to<br />
the RACF resource:<br />
STGADMIN.ADR.STGADMIN.COPY (for <strong>FDR</strong>COPY)<br />
STGADMIN.ADR.STGADMIN.DUMP (for backups)<br />
STGADMIN.ADR.STGADMIN.RESTORE (for restores)<br />
STGADMIN.ADR.STGADMIN.PRINT (for <strong>FDR</strong>DSF PRINT)<br />
in class FACILITY or the equivalent in other security systems, but the security check failed.<br />
A control card error is issued and the operation terminates. If the user cannot be<br />
authorized to these resources, remove the STGADMIN operand so that normal <strong>FDR</strong><br />
security checking is done (see Section 80.15 “Security”).<br />
CHAPTER 100 – PAGE 100-18 –