FDR V54L78 - Innovation Data Processing

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 –