FDR V54L78 - Innovation Data Processing

More documents

Recommendations

Info

FDR315 Reason: Action: MESSAGES AND CODES MESSAGES FROM FDR, DSF, AND ABR (FDRNNN) 100.3 DDNAME=ddn, VOL=SER=vvvvvv NOT ELIGIBLE FOR function MAXIMUM RUNS EXCEEDED 1.The ABR Model DSCB on this volume does not indicate that the volume is enabled for ARCHIVE or SCRATCH (Superscratch) or the ABR Model DSCB does not exist. 2.If MAXIMUM RUNS EXCEEDED is printed, more than 255 Archive Backups of this volume were done today; this limit is only enforced when the backups must be cataloged in the ABR catalog (see “Tape Format and Naming Conventions” in Section 51.1). This volume is bypassed. If you intend to do Archive Backup or Superscratch on this volume, create or update the ABR Model DSCB with FDRABRM (Section 50.40 “VTOC Maintenance Utility (FDRABRM)”) or ISPF panel A.I.8 (Section 90.42 “Set ABR Disk Volume Processing Options”). If the operand “NOINIT” is specified, ABR allows a simulation (SIM TYPE=) of the volume to continue. CHAPTER 100 – PAGE 100-62 –
MESSAGES AND CODES MESSAGES FROM FDR, DSF, AND ABR (FDRNNN) 100.3 FDR316 function status REQUESTED DSN/DSG=dsname VOL=vvvvvv Reason: A SELECT or EXCLUDE statement was input to an FDR program, but none of the data sets processed by that program matched the data set name, dsname mask, or data set group name (“dsname”) on that statement. This is probably an error, since there must have been a reason for providing the statement. “vvvvvv” is the volser if specified by VOL= on the SELECT or if selected from the catalog by CATDSN=. If “status” is DID NOT FIND: ❖ for backups, no data set on the input disks matched the name specification. ❖ for DSF restores, it means that no such data set was found on the input backup files. ❖ for ABR restores, it means that Volume Backup information or Archive Backup information could not be located. This can also be caused by an EXCLUDE preceding the SELECT for the same data sets. Another error (such as message FDR325) may also cause the data sets not to be selected. Action: If “status” is EXCLUDED, the message simply documents that the named data sets were excluded. If “dsname” is MOUNT, then an ABR MOUNT statement did not select any volumes for ABR processing. If an ABR full-volume dump was forced (see message FDR310), then SELECT statements were not processed, and message FDR316 appears for every SELECT. However, all data sets on the volumes were dumped. If this is an error, correct and resubmit job. If you did not expect to get this message, there is probably some error in your SELECT statements; check them. One common error: if you have more than one SELECT statement, and an earlier one selects all the data set that would be selected by a later one, the later one gets the FDR316. For example, SELECT DSN=A.B.** SELECT DSN=A.B.C In general, put the SELECT statements with the most restrictive selection first. This message usually causes the FDR step to end with an ABEND or non-zero return code. If you expect to get this error (perhaps because some data sets may not always exist) and want to ignore it, specify SELTERR=NO on the DUMP statement. NOTE: If the FDR316 message appears in the job log of a batch job and is followed by a system ABEND S213-04 this does not indicate an error in ABR. It is generated by a recall that was invoked by the ABR Data Set Not Found (DSNF) exit. The DSNF exit is entered from OPEN whenever a program tries to OPEN a data set but the DSCB for that data set was not found in the VTOC of the allocated volume. The exit invokes ABR to recall the data set just in case it was archived; however, if it is not found in the Archive Control File, the FDR316 message is printed to show this, probably because it was never archived. This usually means that the data set name was misspelled by the user or the wrong volume serial was given. It can also be caused by trying to OPEN a VSAM cluster with a non-VSAM OPEN that looks for the cluster name instead of the component names in the VTOC. FDR317 I/O ERROR ON DISK TRACK X'cccchhhh' I/O ERROR ON DISK - DDNAME ddname - SEEK ADDRESS cccchhhh Reason: Action: ABR encountered an I/O error while reading or writing the VTOC. The FDR mini-dump is printed. ABR continues processing the VTOC bypassing this track. Contact INNOVATION DATA PROCESSING for assistance. CHAPTER 100 – PAGE 100-63 –
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: 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 61: MESSAGES AND CODES MESSAGES FROM FD
Page 113 and 114:
MESSAGES AND CODES CHAPTER 100 - PA
Page 115 and 116:
MESSAGES AND CODES MESSAGES FROM FD
Page 117 and 118:
FDR908 Reason: Action: MESSAGES AND
Page 119 and 120:
FDR927 Reason: Action: MESSAGES AND
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

Create successful ePaper yourself

Delete template?

Save as template?