FDR V54L78 - Innovation Data Processing

MESSAGES AND CODES
MESSAGES FROM FDR, DSF, AND ABR (FDRNNN) 100.3
Action:
K – LASTAPE was specified but the TAPEx DD specified more than one tape
volume serial.
L – Most likely causes are:
– DYNTAPE was specified to dynamically allocate the backup
medium but a TAPE# DD statement is in the JCL. Remove it; it is
required for DYNTAPE dynamic allocation.
– A TAPEx DD statement was present on a TYPE=DRP restore.
This is not permitted.
M – COPY or MOVE was specified. The TAPEx DD statement for the target
volume was not a disk or specified DD DUMMY.
N – The TAPEx DD statement specified the same volume serial as the DISKx
DD statement.
O – Internal error detected by module FDRDSKTP. Contact INNOVATION
DATA PROCESSING for assistance.
Q – An ABR dump specified DISK as the backup medium (TAPEx). ABR found
that the volume to be dumped (DISKx) was the same as the backup
medium (TAPEx). You cannot backup a volume to itself; it is bypassed.
R – ABR space allocation was not successful for a backup data set on any of the
disk volumes specified by the TAPEx DD statement. Possible reasons are:
– The output disk volumes may be full or have insufficient space for
this backup.
– The backup data set name being allocated already exists on the
output volume (possibly due to an aborted ABR run). Scratch the
duplicate backup data set and run the backup again.
– The output disk volumes are SMS-Managed (not supported for
ABR output disks).
S – SUBSYS= is not supported on TAPE DD statements with DUMP
TYPE=ARC unless SCRATCH=NO is also specified (making it an
application backup).
T – User specified multiple TAPEx DD statements using the same last
character (x). The first one specified DUMMY.
U – Dynamic allocation or OPEN of the backup data set on a disk volume failed.
Check the job log for IBM error messages or the SYSPRINx printouts for
FDR error messages.
Take appropriate action for the problem described by the message.
FDR325 FDRABR NO DISK DD STATEMENTS FOUND
Reason: The ABR step did not identify any disk volumes to be processed. Disk volumes can be
identified to ABR by:
1. DD statements having DDnames starting with DISK.
2. The ONLINE operand (all online volumes).
3. MOUNT statements.
4. The ONLVOL operand (requires that volumes be identified by SELECT
statements with either VOL=, VOLG=, or CATDSN= operands.
Items (3) and (4) can cause message FDR325 if none of the identified volumes are
online. If this is a job that processes an ABR remote queue data set, the message can
also occur if the remote queue is empty.
Action: Change the jobstream to properly identify the disk volumes to be processed.
CHAPTER 100 – PAGE 100-68 –