FDR V54L78 - Innovation Data Processing
FDR V54L78 - Innovation Data Processing
FDR V54L78 - Innovation Data Processing
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
CPK521x<br />
Reason:<br />
CPK522E<br />
Action:<br />
Reason:<br />
Action:<br />
CHAPTER 100 – PAGE 100-134 –<br />
MESSAGES AND CODES<br />
COMPAKTOR MESSAGES (CPKNNNXX) 100.6<br />
DSCB AT CCHHR(HEX) -- cccchhhhrr -- HAS INCORRECT EXTENT DESCRIPTOR<br />
FLAGS<br />
One or more extent descriptions in a DSCB have invalid flags. “cccchhhhrr” is the disk<br />
address of the DSCB (cylinder, track, and record, in hex). This can occur if:<br />
1. Flags indicate that the extent begins and ends on a cylinder boundary, when in<br />
fact it does not (message CPK521W).<br />
2. A flag indicating that the extent is a user label extent (LABEL=(,SUL)) was found<br />
on, but the extent is not the first extent (message CPK521E).<br />
3. Flags indicate extent is a shared (split) cylinder, not supported by z/OS or<br />
COMPAKTOR (message CPK521E).<br />
For problem (1), COMPAKTOR fixes the problem as long as the data set is moved or<br />
has free space released. For problems (2) and (3), list the VTOC as described under<br />
message CPK516E. Locate the DSCB in error and determine which problem it is, and<br />
superzap the bad DSCB to fix the problem. Contact INNOVATION DATA<br />
PROCESSING for assistance.<br />
DSCB AT CCHHR(HEX) -- cccchhhhrr -- HAS AN INVALID CHAIN POINTER OR COUNT FIELD<br />
Either the count field (hardware record ID) of the chain pointer (pointer to the next DSCB<br />
for this data set) was invalid. “cccchhhhrr” is the disk address of the DSCB (cylinder,<br />
track, and record, in hex). This can occur if:<br />
❖ The count field of the specified DSCB does not match its physical location.<br />
❖<br />
❖<br />
The chain pointer in a Format 1 or 2 DSCB is invalid (does not point to a record in<br />
the VTOC).<br />
The chain pointer in a Format 3 DSCB is not zero for data sets that cannot exceed<br />
16 extents.<br />
Use <strong>FDR</strong>DSF PRINT (see Section 20.5 “DSF PRINT Statement”) to print the track<br />
where the DSCB resides and determine what field is in error. If the count field is in<br />
error, you have a serious problem and should contact IBM. If the chain pointer in a<br />
Format 1 or 2 DSCB is invalid, you can attempt to superzap the DSCB.<br />
CPK523E DSCB AT CCHHR(HEX) -- cccchhhhrr -- HAS AN INVALID NUMBER OF EXTENTS<br />
Reason: The extent count in a Format 1 DSCB was invalid. “cccchhhhrr” is the disk address of<br />
the DSCB (cylinder, track, and record, in hex). This can occur if the extent count is<br />
greater that 128 for VSAM clusters and some SMS-Managed data sets, or greater<br />
than 16 for other data sets.<br />
Action: This is a serious problem. Determine the error type and attempt to fix the DSCB in error.<br />
CPK524E DSCB AT CCHHR(HEX) -- cccchhhhrr -- DESCRIBES AN EXTENT WHICH<br />
OVERLAPS SOME OTHER EXTENT.<br />
OVERLAPPING EXTENT'S LOW AND HIGH CCHH(HEX) -- cccchhhh-cccchhhh<br />
Reason: See associated CPK525E message.<br />
Action: See associated CPK525E message.<br />
CPK525E<br />
DSCB AT CCHHR(HEX) -- cccchhhhrr -- IS THE OTHER DSCB INVOLVED IN OVERLAP.<br />
OVERLAPPED EXTENT'S LOW AND HIGH CCHH(HEX) -- cccchhhh-cccchhhh<br />
Reason: COMPAKTOR has detected that two extent descriptor fields, in Format 1 or 3 DSCBs,<br />
claim ownership of the same track or tracks. This is a serious error. The data may be<br />
incorrect in either or both data sets. “cccchhhhrr” is the disk address of the DSCB<br />
(cylinder, track, and record, in hex). “cccchhhh” describes the overlapping extents<br />
(cylinder and track, in hex).<br />
Action: Determine the contents of the overlapped area and eliminate or fix one of the DSCBs<br />
involved. If one of the DSCBs is a Format 3 that has no F1/F2 pointing to it, then that is the<br />
one to be eliminated. Use SUPERZAP to zero out this DSCB (see message CPK516E).