FDR V54L78 - Innovation Data Processing

MESSAGES AND CODES
MESSAGES FROM FDR, DSF, AND ABR (FDRNNN) 100.3
Action:
X – A DSF absolute track restore was requested (SELECT FROM/TO) and
cylinder or track numbers were specified that are invalid for the type of disk
that was backed up.
Y – OLDBACKUP was specified. The data set does not contain as many levels
of OLDBACKUP information as requested by the OLDB=nn operand or the
specified backup is no longer in the ABR catalog.
Z – An ABR data set restore was requested and a TAPEx DD statement was
provided, but the backup containing this data set occupies more than 5 tape
volumes. To restore this data set, remove the TAPEx DD and specify the
DYNTAPE option. This code also occurs if you use the TAPED=x operand on
an archive restore (TYPE=ARC) or application restore (TYPE=APPL).
Take appropriate action for the problem described by the message.
FDR323 DDNAME=DISKdddd DOES NOT SPECIFY A DISK
Reason: DD statements whose DDnames start with DISK must point to a disk device.
Action: Correct and resubmit job.
FDR324 DDNAME=dddddddd IS MISSING OR IN ERROR REASON=x
Reason: A failure has occurred for DDname specified in the message. In the reason text below,
“Control File” refers to the Archive Control File for Archive Backups, and to the
Application Control File for Application Backups. The reason code “x” may be:
1 – SYSIN DD statement missing.
2 – I/O error on SYSIN data set or remote queue data set.
3 – ARCHIVE DD statement missing and DYNARC was not specified.
4 – Control File block size is zero. The file may have been allocated but never
initialized. If so, use FDRARCH to initialize it.
5 – I/O error on Control File.
6 – The date of the last Archive or Application backup, as recorded in the
Control File, is higher than the current system date; this might occur if you
did backups while you had the system date set ahead for YEAR2000
testing. To override the ABR date check, specify PROT=NONE on the
DUMP statement of next Archive or Application job using that Control
File only. The Control File will be out of date sequence.
7 – A block of the Control File did not contain ABR identifiers. The Control File
may have been overwritten by another program. You may be able to restore
a backup of the most recent Control File. Please call INNOVATION DATA
PROCESSING for assistance.
8 – The Control File is full. You can reorganize or expand it with FDRARCH. If
you are using the option of Application Backup to create the Control File,
increase the space allocated.
9 – The number of TAPEx DD statements exceeded 9.
A – No TAPEx DD statements were specifying tape or disk backup were found.
ABR ignores DD DUMMY statements
B – The number of DISKxxxx DD statements plus any volumes selected by
ONLINE, ONLVOL, and MOUNT was greater than the value specified in the
MAXDD operand (default of 256).
D – A SYSPRINx DD statement was missing. ABR requires a SYSPRINx DD
statement for each TAPEx DD statement.
E – A DISKx DDname was used more than once in the JCL for this step.
F – A FDR or FDRDSF backup specified DISP=MOD on the TAPEx DD card. Also
occurs if the TAPEx DD refers to a subsystem data set (such as ExHPDM) via
the SUBSYS= JCL parameter, and the RTC=YES operand was also specified
on the DUMP statement; these are not compatible. The disk volume associated
with this tape is not processed.
I – OPEN failed for the backup file. Check the job log for IBM error messages.
CHAPTER 100 – PAGE 100-67 –