30.01.2015 Views

FDR V54L78 - Innovation Data Processing

FDR V54L78 - Innovation Data Processing

FDR V54L78 - Innovation Data Processing

SHOW MORE
SHOW LESS

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

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

MESSAGES AND CODES<br />

MESSAGES FROM <strong>FDR</strong>, DSF, AND ABR (<strong>FDR</strong>NNN) 100.3<br />

<strong>FDR</strong>316 function status REQUESTED DSN/DSG=dsname VOL=vvvvvv<br />

Reason: A SELECT or EXCLUDE statement was input to an <strong>FDR</strong> program, but none of the data<br />

sets processed by that program matched the data set name, dsname mask, or data<br />

set group name (“dsname”) on that statement. This is probably an error, since there<br />

must have been a reason for providing the statement. “vvvvvv” is the volser if<br />

specified by VOL= on the SELECT or if selected from the catalog by CATDSN=.<br />

If “status” is DID NOT FIND:<br />

❖ for backups, no data set on the input disks matched the name specification.<br />

❖ for DSF restores, it means that no such data set was found on the input backup files.<br />

❖ for ABR restores, it means that Volume Backup information or Archive Backup<br />

information could not be located.<br />

This can also be caused by an EXCLUDE preceding the SELECT for the same data sets. Another<br />

error (such as message <strong>FDR</strong>325) may also cause the data sets not to be selected.<br />

Action:<br />

If “status” is EXCLUDED, the message simply documents that the named data sets<br />

were excluded.<br />

If “dsname” is MOUNT, then an ABR MOUNT statement did not select any volumes for<br />

ABR processing.<br />

If an ABR full-volume dump was forced (see message <strong>FDR</strong>310), then SELECT<br />

statements were not processed, and message <strong>FDR</strong>316 appears for every SELECT.<br />

However, all data sets on the volumes were dumped.<br />

If this is an error, correct and resubmit job. If you did not expect to get this message, there is<br />

probably some error in your SELECT statements; check them. One common error: if you<br />

have more than one SELECT statement, and an earlier one selects all the data set that<br />

would be selected by a later one, the later one gets the <strong>FDR</strong>316. For example,<br />

SELECT DSN=A.B.**<br />

SELECT DSN=A.B.C<br />

In general, put the SELECT statements with the most restrictive selection first.<br />

This message usually causes the <strong>FDR</strong> step to end with an ABEND or non-zero return<br />

code. If you expect to get this error (perhaps because some data sets may not always<br />

exist) and want to ignore it, specify SELTERR=NO on the DUMP statement.<br />

NOTE: If the <strong>FDR</strong>316 message appears in the job log of a batch job and is followed by a<br />

system ABEND S213-04 this does not indicate an error in ABR. It is generated by<br />

a recall that was invoked by the ABR <strong>Data</strong> Set Not Found (DSNF) exit. The DSNF<br />

exit is entered from OPEN whenever a program tries to OPEN a data set but the<br />

DSCB for that data set was not found in the VTOC of the allocated volume. The<br />

exit invokes ABR to recall the data set just in case it was archived; however, if it is<br />

not found in the Archive Control File, the <strong>FDR</strong>316 message is printed to show this,<br />

probably because it was never archived. This usually means that the data set<br />

name was misspelled by the user or the wrong volume serial was given. It can<br />

also be caused by trying to OPEN a VSAM cluster with a non-VSAM OPEN that<br />

looks for the cluster name instead of the component names in the VTOC.<br />

<strong>FDR</strong>317 I/O ERROR ON DISK TRACK X'cccchhhh' I/O ERROR ON DISK - DDNAME ddname -<br />

SEEK ADDRESS cccchhhh<br />

Reason:<br />

Action:<br />

ABR encountered an I/O error while reading or writing the VTOC. The <strong>FDR</strong> mini-dump is<br />

printed.<br />

ABR continues processing the VTOC bypassing this track. Contact INNOVATION DATA<br />

PROCESSING for assistance.<br />

CHAPTER 100 – PAGE 100-63 –

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!