FDR V54L78 - Innovation Data Processing

MESSAGES AND CODES
MESSAGES FROM FDR, DSF, AND ABR (FDRNNN) 100.3
C –
D –
E –
F –
G –
H –
I –
J –
K –
L –
M –
N –
More than one SYS1.VVDS data set found on the volume. The operating
system uses the VVDS that contains the current disk volume serial number
in the name. More than one VVDS can be created if a volume with a VVDS
is renamed and a VSAM cluster is allocated using the volume with the new
serial number. If the VVDS with the incorrect volume serial does not have
any current clusters cataloged within it, use SUPERZAP to turn off the
PASSWORD indication in the DSCB and scratch the data set using
IEHPROGM. A backup completes but no VSAM clusters are restored from it
and non-VSAM SMS data sets may not be restorable. A restore issues an
U0634 ABEND, so no VSAM or SMS data set restores are done to this
volume until the condition is corrected.
The volume serial in the data set name of the VVDS (SYS1.VVDS.Vvolser)
does not match the volume serial of the disk. This can occur if a volume
was copied or restored to a new disk volume serial but the VVDS was not
renamed. Another possible cause is the DUMPCONDITIONING option of
DFSMSdss. This is only a warning; FDR backs up the volume properly,
using that VVDS. However, VSAM and SMS data sets on the volume are
not usable until the condition is corrected.
FDR did a GETMAIN for above the line storage for a VSAM table but the
GETMAIN failed. Try increasing the REGION= parameter to more than 32M. 1
FDR did not find both a VVR/NVR and a DSCB for a given data set; one was
missing. Also occurs when FDR was unable to calculate the free space in a cluster.
The imbedded index VVR (Type Q) was not found. (See Note 2 below.)
The size of an extent was not a multiple of the CA size; or the high RBA of
an extent exceeded the maximum. On a logical restore, the original cluster
had an imbedded index (the IMBED attribute) and the high-level index
component had more than one extent.
The control interval size (CISIZE) on the backup cluster does not match the
cluster on disk. The displacement is x'16'. 2
The number of CIs per CA on the backup cluster does not match the cluster
on disk. The displacement is x'0E'. 2
The space allocation unit (TRACK vs CYL) on the backup cluster does not
match the cluster on disk. The displacement is x'10'. 2 This error is also
issued following an FDR160 message; see FDR160.
The physical blocksize or number of blocks per track on the backup cluster
does not match the cluster on disk. The displacement is x'11' or x'15'. 2
The number of tracks per CA on the backup cluster does not match the cluster on
disk (check the secondary allocation value specified). The displacement is x'17'. 2
The VSAM cluster is being restored to a different type of cluster, e.g., KSDS to an
ESDS. Flags at two displacements are checked. 2 At displacement x'03' it checks:
x'02' – Relative Record (RRDS)
x'04' – Key Range
x'10' – Replication (REPLICATE)
x'20' – Imbedded Index (IMBED)
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.
2. For the indicated reason codes, FDR prints a mini-dump displaying the VVR (VSAM Volume
Record) from the backup file and from the cluster on disk. In the registers at the top of
the dump, register 14 points to a cell within the disk VVR and register 15 points to a cell
within the backup VVR. Those registers plus the hex displacements shown above for the
appropriate reason codes points to the fields that did not compare.
CHAPTER 100 – PAGE 100-31 –