FDR V54L78 - Innovation Data Processing

More documents

Recommendations

Info

MESSAGES AND CODES MESSAGES FROM FDR, DSF, AND ABR (FDRNNN) 100.3 FDR370 OPEN ERROR -- TAPE BYPASSED DSN=dsname Reason: A full-volume restore operation was requested from this tape. The open of the tape failed. ABR bypasses this tape unless it is the full volume (FDR) backup. Action: Check for IBM OPEN messages in the job log. Data sets that were on this incremental backup may not be restored to their latest status. Contact INNOVATION DATA PROCESSING for assistance. FDR371 FORMAT 4 DSCB NOT FOUND ON RESTORE TAPES Reason: FDR or ABR full-volume restore did not find the Format 4 DSCB (first record of the VTOC) on any of the backup tapes. The restore may not be correct. This can occur if the pointer to the VTOC in the disk volume label was invalid at the time of the dump, or if errors occurred reading the backup records containing the VTOC. Action: Contact INNOVATION DATA PROCESSING for assistance. FDR372 DISK FORMAT 4 READ ERROR Reason: An I/O error occurred reading the Format 4 DSCB (first record on the VTOC) of the output disk volume during a full-volume restore. The pointer to the next available alternate track on the volume, stored in the Format 4, if any, are lost, but the volume is probably usable. A mini-dump is printed, showing the I/O error. Action: Run a COMPAKTOR MAP to check for VTOC errors. Contact INNOVATION DATA PROCESSING for assistance. FDR373 UCB VTOC LOCATION WAS NOT UPDATED Reason: FDR failed to locate the disk label record on the backup tape (Cylinder 0 Track 0 Record 3) during a full-volume restore. The volume was restored, but the system pointers to the VTOC, VTOC Index, and VVDS were not updated. The output volume may not have a volume label. Action: Use FDRDSF with “PRINT TYPE=DSF,DSN=VTOC” to print the label track and VTOC to verify that the VOL1 volume label exists on CYL 0 TRK 0; if not, contact INNOVATION DATA PROCESSING for assistance. If so, vary the volume offline and then remount it to update the system pointers. FDR374 BACKUP TAPE DID NOT CONTAIN THE ABR MODEL Reason: FDRABR failed to locate the ABR Model DSCB in the control records at the beginning of the first incremental backup read during an ABR full-volume recovery. A normal incremental backup always contains the ABR Model DSCB, so this is not normal (perhaps the ABR Model DSCB was excluded by an EXCLUDE statement. Action: If the output volume contains an ABR Model DSCB and has the same serial as the volume being restored, the restore terminates with an U0304 ABEND. If not, the restore proceeds; this message is issued once for each incremental that does not contain the ABR Model DSCB; some data sets may not be restored correctly. FDR375 ABR MODEL OR VTOC INDEX REWRITE/RENAME/ALLOC FAILED Reason: An error occurred when FDR attempted to rewrite or allocate the ABR Model DSCB, or rename the index VTOC or ABR Model DSCB. The user may not be authorized to create, rename, or update this data set. Action: This volume may need to be re-initialized for ABR processing, or the indexed VTOC may need to be rebuilt with ICKDSF. Contact INNOVATION DATA PROCESSING for assistance. CHAPTER 100 – PAGE 100-78 –
MESSAGES AND CODES MESSAGES FROM FDR, DSF, AND ABR (FDRNNN) 100.3 FDR376 MULTIPLE ABR MODELS FOUND ON BACKUP DSN=dsname Reason: FDR found more than one ABR Model DSCB on the backup tape during a full-volume restore. The first one encountered is the one used. The disk volume serial number or the ABR Model DSCB name may have been changed prior to the dump without using the ABR maintenance programs. Action: SCRATCH the incorrect model using IEHPROGM specifying PURGE on the SCRATCH command. Use program FDRABRM with a REMODEL command (see Section 50.44 “FDRABRM REMODEL Statement”) or the ABR ISPF dialogs (see Section 90.15 “ABR Options”) to reset the remaining ABR Model DSCB to the correct Generation and Cycle number. Contact INNOVATION DATA PROCESSING for assistance. FDR377 DISK PACK HAS BEEN RELABELED TO VOL=vvvvvv Reason: Information message indicating that the volume serial of the disk being restored to has changed by a full-volume restore. Action: If disk is shared by multiple systems, it should be varied offline and remounted to the other systems. FDR378 RENAME FAILED COMP=cccc CODE=code FROMDSN=tempname NEWDSN=permname CLUSTER=clusname Reason: On an FDRCOPY MOVE or RESTORE of a VSAM cluster to the same name, the output cluster and its components were initially created with temporary names (an index level starting with T is inserted). After the input data set was deleted, FDRCOPY attempted to ALTER the temporary names back to the original cluster and component names but an error occurred. “cccc” is the return code and “code” is the reason code from ALTER; look up these codes under IBM message IDC3009I in the IBM message manuals. If “cccc” is 04nn, then “nn” is the return code from a RENAME SVC; if it is 05nn, then it is a return code from the SMS RENAME service. “tempname” is the temporary cluster or component name that FDRCOPY was trying to rename back to “permname”. “clusname” is the original name of the cluster if the rename failed on a component. Action: If an FDR378 is not issued for the cluster itself, it was renamed successfully and the cluster can be used under its original name. If an FDR378 was issued for the cluster, the cluster was not renamed. It can be used under its temporary name “tempname”, but you probably want to check the error codes and ALTER the cluster to its original name if possible. If FDR378 messages were issued for one or more components, those components were not renamed. The cluster is usable, but you may want to check the error codes and ALTER the component to its original name if possible. If needed, contact INNOVATION DATA PROCESSING for assistance. FDR390 DSF NO DATA SETS MET SELECTION CRITERIA Reason: No data sets were selected from the current disk volume. For an ABR step, this means that neither SELECT statements nor ABR automatic criteria (e.g., the update flag for Volume Backup) selected data sets on this volume. Action: This may be normal if there were simply no data sets that met ABR requirements on the volume at this time. Otherwise check your SELECT statements and correct any errors. FDR391 OPERATOR REPLIED NO TO ARCHIVE ON UNEXPIRED DSN=dsname Reason: ABR selected a data set for Archive Backup or Superscratch whose expiration date has not been reached. The operator replied “NO” to the FDRW23 message. Action: The data set is bypassed. If the EXPD=NONE operand is specified on the DUMP statement, ABR does not perform this check. CHAPTER 100 – PAGE 100-79 –
Page 1 and 2:
MESSAGES AND CODES INTRODUCTION TO
Page 3 and 4:
MESSAGES AND CODES FDR CONSOLE MESS
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
MESSAGES AND CODES MESSAGES FROM FD
Page 19 and 20:
FDR020 Reason: Action: MESSAGES AND
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28: MESSAGES AND CODES CHAPTER 100 - PA
Page 29 and 30: FDR142 Reason: Action: MESSAGES AND
Page 31 and 32: MESSAGES AND CODES MESSAGES FROM FD
Page 77: MESSAGES AND CODES MESSAGES FROM FD
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?