FDR V54L78 - Innovation Data Processing

MESSAGES AND CODES
COMPAKTOR MESSAGES (CPKNNNXX) 100.6
CPK513E INVALID REQUEST TO ELIMINATE UNUSED TRACKS FOR DATA SET- dsname.
DATA SET IS EITHER UNMOVABLE, UNCHANGEABLE, OR IS NOT A SEQUENTIAL
OR PARTITIONED DATA SET.
Reason: A SELECT statement specified “dsname” and requested that unused tracks or extents
be freed. However, the data set is ineligible for this action.
Action: Correct control statement in error and rerun.
CPK514W POSSIBLE FORMAT 5 ERRORS IN VTOC.
Reason: 1.Either no Format 5 DSCBs exist or they are incorrect.
CPK515E
Action:
Reason:
CPK516E
Action:
Reason:
Action:
2. The “contamination” bit is on in the Format 4 DSCB, or the volume is a DOS (VSE) volume.
If COMPAKTing, none required since COMPAKTOR fixs this problem. If mapping or simulating,
either fix the VTOC yourself, or COMPAKT the volume so that COMPAKTOR fixes it for you.
NON-STANDARD VTOC DETECTED. FORMAT 4 DSCB IS NOT THE FIRST RECORD
OF FIRST VTOC TRACK
VTOC does not conform to IBM operating system standards. The first DSCB in the
VTOC is not a Format 4 DSCB. This can also occur if the VTOC contains more than
one Format 4 DSCB, which is also invalid. COMPAKTOR cannot process this volume.
COMPAKTOR bypasses this volume, which may have to be initialized. Contact
INNOVATION DATA PROCESSING for assistance.
DSCB AT CCHHR(HEX) -- cccchhhhrr -- IS PART OF A BROKEN F1-F2-F3 DSCB
CHAIN
Either a Format 1 or Format 2 DSCB does not point to a Format 3 when it should; or a
Format 2 or Format 3 DSCB has no F1/F2 DSCB pointing to it. “cccchhhhrr” is the
disk address of the DSCB (cylinder, track, and record, in hex).
List the VTOC using the IBM IEHLIST utility, e.g.,
//LIST EXEC PGM=IEHLIST
//SYSPRINT DD SYSOUT=*
//DISK1 DD UNIT=SYSALLDA,VOL=SER=vvvvvv,DISP=OLD
//SYSIN DD *
LISTVTOC VOL=3390=vvvvvv,DUMP
/*
In that listing, the disk address of each DSCB is printed on the right side of the third line
for that DSCB. Locate the DSCB in error and attempt to fix the error condition.
If the DSCB identified by CPK516E is a Format 3, you can zap the DSCB to all binary
zeros and then run a COMPAKTion to correct the VTOC. Sample JCL to do this zap is
in member F3CLEAR in the FDR Installation Control Library (ICL).
WARNING:
Message CPK516E may occur for conditions other
than unchained F3 DSCBs, although that is the
most common cause. DO NOT run the zap job until
you have verified that all DSCBs identified in
CPK516E messages are F3 DSCBs that are not
themselves chained to another F3 DSCB (their last
5 bytes must be zero).
CPK517E DATA SET NOT FOUND, OWNS NO EXTENTS, OR IS UNMOVABLE -- dsname
Reason: Data set “dsname”, specified on a SELECT DSNAME statement, was not found, was a
model DSCB (no space allocated), or was unmovable. See “Unmovable Data Sets” in
Section 40.4 for a list of the types of data sets that COMPAKTOR considers to be
unmovable.
Action: Correct the error and rerun.
CHAPTER 100 – PAGE 100-132 –