FDR V54L78 - Innovation Data Processing

More documents

Recommendations

Info

MESSAGES AND CODES MESSAGES FROM FDR, DSF, AND ABR (FDRNNN) 100.3 FDR155 nnnnn TRACKS MISSING ON function OF DSN=dsname Reason: Data set RESTORE, COPY, or MOVE detected that a number of expected tracks were not found during the restore of the data set “dsname”. “nnnnn” is the number of tracks that were not found. The remainder of the data set was restored, but it may be unusable. The cause may be: ❖ The restore specified DATA=ALL, but the backup used DATA=USED. ❖ The restore used DATA=ALL or DATA=USED but the backup was created with DATA=NONE. ❖ The restore used LBPZERO=INVALID, but the backup used LBPZERO=VALID. ❖ Backup file errors (message FDR200) were reported during the backup or restore. ❖ A disk error occurred during the backup that required tracks or cylinders to not be recorded on the backup file (e.g., message FDR123 or FDR129). Message FDR150 is also printed for such tracks during the restore. ❖ Blocks were lost from the backup file due to unreported tape drive errors. ❖ The restore subtask ABENDed before completing the restore (message FDR997 is also issued). Action: If the cause cannot be determined, contact INNOVATION DATA PROCESSING for assistance. FDR156 Reason: ALLOCATE FAILED FOR nnnnn quan COMP=X'code-reason' VOL=vvvvvv DSN=dsname ALLOCATE FAILED FOR CATALOG COMP=comp CODE=reason VOL=vvvvvv DSN=dsname FDR attempted to allocate a non-VSAM data set “dsname” on volume “vvvvvv” and the attempt failed (if “FAILED FOR CATALOG” is displayed, the allocation was successful, but a later attempt to catalog the data set failed; this can also occur for VSAM). “nnnnn” is the size of the data set that failed allocation in tracks or cylinders, “quan” is TRK or CYL. If the allocation was attempted on multiple volumes (because of the NVOL= operand or the ABR RESTORE ALLOCATION LIST), it failed on all of them, but “vvvvvv” is the first volume where it was tried, and “comp” is the error code from that volume. If the data set is SMS-Managed, “vvvvvv” is the volume that FDR selected for the data set and may not be the same as the volume where SMS tried to allocate it. “comp” may be return codes from the IBM ALLOCATE SVC (SVC 32), from the IBM CATALOG SVC (SVC 26), from the IBM SMS interface, or internal diagnostic codes from FDR itself. If “FAILED FOR CATALOG” is displayed, “comp” is the return code and “reason” is the reason code from the CATALOG SVC, in decimal, as documented for the IBM message IDC3009I. Some of the common catalog codes shown under message FDR157 also apply to FDR156. Note that if “comp” is 51, look up the “reason” code under code 50 in message IDC3009I. If “comp” is 300, this is an internal error; contact INNOVATION DATA PROCESSING for assistance. If “comp” is 9xxx, contact INNOVATION DATA PROCESSING for assistance. “reason” equal to 00040 may mean an attempt to catalog a GDG generation when the GDG base does not exist. Otherwise, if “comp” is a value less than x'1000', it is from the ALLOCATE SVC, in hex. “reason” may be a 8-digit hex IBM diagnostic code. For z/OS and ESA see the IBM manual DFSMSdfp Diagnosis Reference. Common ALLOCATE codes include: 0004 – Duplicate data set name in VTOC; data set already exists on the volume. This may occur for multi-volume data sets if the piece currently on the volume has a different volume sequence number than the piece being restored. 0008 – VTOC or VTOC index (VTOCIX) is full. 000C – I/O error in VTOC or VTOC index (VTOCIX) 0010 – Requested absolute tracks not available; an unmovable data set cannot be allocated because the required tracks are not free. 0014 – Requested space quantity not available; DADSM was unable to find sufficient free space (in up to 5 extents) to allocate the data set, or the specific space required for an unmovable data set was not free. CHAPTER 100 – PAGE 100-34 –
MESSAGES AND CODES MESSAGES FROM FDR, DSF, AND ABR (FDRNNN) 100.3 Action: 00AC – No security authorization to create data set. You must have ALTER authority to the data set under IBM RACF or the equivalent in other security systems. 00B4 – IGGPRE00 installation exit rejected the request. A local exit or DASD control software product has disallowed allocation on the volume that FDR selected. 00C0 – SMS failed the allocation request. The most common cause is a mismatch between the SMS flags in the VTOC of the output volume and that volume’s status in the current SMS configuration; common reason codes are: 04160053 – VTOC indicates INITIAL status (in process of conversion to SMS). 04160054 – VTOC indicates non-SMS, but the volume is in an SMS storage group. 04160055 – VTOC indicates SMS, but the volume is not in an SMS storage group. You can use FDRCONVT (Section 70.30 “FDRCONVT Overview”) to convert the volume to SMS or non-SMS, or you can remove the volume from its storage group in the current SMS configuration. “comp” values greater than 1000 are from FDR, in hex, as follows: 2354 – The name of the data set being restored does not meet IBM's data set naming conventions. If NEWNAME=, NEWGROUP=, or NEWINDEX= was specified, the error is in the new name; otherwise it is the original name of the data set that is invalid. You can bypass this check by specifying NODSNCHK on the RESTORE statement; the data set is allocated but the catalog probably fails. FDxx – The IBM subsystem interface (IEFJSREQ) failed with return code “xx”. FExx – The IBM SMS interface failed the allocation request with return code “xx”, (usually 08). “reason” is an SMS error code, in decimal. You can find the description by looking up IBM message IGDxxxxx, where “xxxxx” is the reason code. FF04 – FDR cannot allocate an ISAM file. See member ISAM in Installation Control Library (ICL). FF08 – FDR cannot allocate a non-ICF VSAM file. FF0C – FDR cannot allocate an unmovable file with more than three extents. FF18 – On a COPY/MOVE of a data set protected by a discrete RACF profile, an attempt to issue RACDEF to define a profile for the output data set failed. “reason” is “0000xxyy” where “xx” is the RACF return code and “yy” the RACF reason code (“xx” of 04 indicates that the profile already exists, 08 that the user is not authorized to create the profile). FF50 – GETMAIN failure during allocation. Increase the region. FF51 – Allocation parameter list error. Contact INNOVATION DATA PROCESSING. FF52 – FDR did not select a target output volume. This can occur if the data set's original volume or the volume you specified as NVOL= is not online. Specify a new NVOL= value or update the ABR Restore Allocation List to direct the data set to an online volume. FF53 – NVR is not record type N. Contact INNOVATION DATA PROCESSING. FF54 – NVR cell type not 22. Contact INNOVATION DATA PROCESSING. FF55 – NVR type 24 cell length invalid. Contact INNOVATION DATA PROCESSING. FF56 – NVS SMS sub-cell not type 24. Contact INNOVATION DATA PROCESSING. FF57 – DSCB address not passed. Contact INNOVATION DATA PROCESSING. FF58 – The selected target disk volume was SMS-Managed, but no storage class was assigned. It may be that your SMS Automatic Class Selection (ACS) routines are assigning a null storage class to this data set. To restore as SMS, specify STORCLAS=; if it still fails, use BYPASSACS or update your Automatic Class Selection (ACS) routines. To restore as non-SMS, specify NVOL= to direct it to a non-SMS volume. FF59 – Volsers in CPL cannot be located, or over 10 volumes passed. Contact INNOVATION DATA PROCESSING. Determine the cause and take appropriate action. It may be possible to circumvent the problem by pre-allocating the output data set. If needed, contact INNOVATION DATA PROCESSING for assistance. CHAPTER 100 – PAGE 100-35 –
Page 1 and 2: MESSAGES AND CODES INTRODUCTION TO
Page 3 and 4: MESSAGES AND CODES FDR CONSOLE MESS
Page 17 and 18: MESSAGES AND CODES MESSAGES FROM FD
Page 19 and 20: FDR020 Reason: Action: MESSAGES AND
Page 27 and 28: MESSAGES AND CODES CHAPTER 100 - PA
Page 33: MESSAGES AND CODES MESSAGES FROM FD
Page 59 and 60: MESSAGES AND CODES CHAPTER 100 - PA
Page 85 and 86:
MESSAGES AND CODES CHAPTER 100 - PA
Page 87 and 88:
MESSAGES AND CODES MESSAGES FROM FD
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
FDR547 Reason: Action: MESSAGES AND
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
FDR939 Reason: MESSAGES AND CODES T
Page 123 and 124:
MESSAGES AND CODES MESSAGES FROM SA
Page 125 and 126:
100.6 COMPAKTOR MESSAGES (CPKNNNXX)
Page 127 and 128:
CHAPTER 100 - PAGE 100-127 - MESSAG
Page 129 and 130:
MESSAGES AND CODES COMPAKTOR MESSAG
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
CPK526E MESSAGES AND CODES COMPAKTO
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
MESSAGES AND CODES FDRREORG MESSAGE
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
MESSAGES AND CODES ABEND CODES 100.
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
100.9 WAIT STATE CODES FROM SAR WAI
show all

FDR V54L78 - Innovation Data Processing

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?