FDR V54L78 - Innovation Data Processing

MESSAGES AND CODES
MESSAGES FROM FDR, DSF, AND ABR (FDRNNN) 100.3
FDR151 I/O ERROR DSN=dsname
I/O ERROR WRITING DISK TRACK X'cccchhhh' VOL=vvvvvv TRACK BYPASSED
Reason: FDR detected an I/O error writing the disk track at cylinder cccc track hhhh (both are in
hex). For a data set restore only, the first FDR151 message identifies the data set that
contains the track.
Action: FDR continues the restore operation. This track is bypassed. See “Disk I/O Errors” in
Section 80.30 for help in understanding the error. Contact INNOVATION DATA
PROCESSING for technical assistance.
NOTE: If this is a logical restore and you also received an FDR138 REASON=9, then
refer to the instructions in the Action for the FDR138 message.
FDR152
Reason:
ICF VSAM ERROR REASON=x DSN=cluster/component VOL=vvvvvv
An I/O error or logical error exists within the SYS1.VVDS data set or in the VVDS information for
the cluster or component indicated on volume “vvvvvv” (this error may also occur for non-VSAM
data sets on SMS-Managed volumes). On a restore, FDR compares the characteristics of the
cluster on the backup file with those of the cluster being restored to on disk; if some required
characteristic does not match, this message details that mismatch. The VVR/NVR from the
backup and the disk is printed for certain types of errors.
The reason code “n” may be:
1 – VSAM clusters exist on the volume, but FDR failed to find the SYS1.VVDS
data set on the output disk or on the backup file. The VVDS may not exist or
FDR encountered an error trying to find it. The IOB details the error. 1
2 – The number of extents in the SYS1.VVDS data set was zero.
3 – The SYS1.VVDS contains more than 3 extents. FDR had an I/O error or
logical error finding a Format 3 DSCB. The IOB details the error. 1
4 – An I/O error or logical error was detected when FDR read or wrote entries within the
SYS1.VVDS data set, or the VVDS contains no active records (even though there
are VSAM clusters on the volume). For an I/O error, the IOB details the error. 1
5 – The length of a VVR/NVR entry within the VVDS is zero or negative. 1
6 – The length of all of the VVR/NVR entries within a block of the VVDS
exceeded the length in use within the block. (See Note 2 below.)
7 – A VVDS record indicates that the length of its in-use data exceeds 4096. 1
8 – An error occurred when DSF attempted to find one of the associated
components for this cluster. The component may be in the VVDS but not in
the VTOC. The IOB details the error.
9 – FDR is unable to store all of the VSAM component and cluster names in its
internal table. A large number of VSAM clusters must exist on the volume.
Specify the keyword ICFCORE= on the DUMP TYPE= statement or
permanently increase the ICFCORE value in the FDR Global Options Table.
A – A cluster specifies a catalog name that was not found in the catalog entries
stored in the first record of the VVDS.
B – FDR could not find the volume information/allocation cell (type 23) in the
VVR record, or an individual cell had an invalid length.
1. If you are executing a SNAP, SPLIT, PSPLIT, or FCOPY function, message FDR152 with
the indicated reason codes prevents the function from completing. If you want the function
to complete despite the message, add the operand “SMSPROT=NONE” to the SNAP,
SPLIT, PSPLIT, or FCOPY statement.
CHAPTER 100 – PAGE 100-30 –