FDR V54L78 - Innovation Data Processing

More documents

Recommendations

Info

CPK521x Reason: CPK522E Action: Reason: Action: CHAPTER 100 – PAGE 100-134 – MESSAGES AND CODES COMPAKTOR MESSAGES (CPKNNNXX) 100.6 DSCB AT CCHHR(HEX) -- cccchhhhrr -- HAS INCORRECT EXTENT DESCRIPTOR FLAGS One or more extent descriptions in a DSCB have invalid flags. “cccchhhhrr” is the disk address of the DSCB (cylinder, track, and record, in hex). This can occur if: 1. Flags indicate that the extent begins and ends on a cylinder boundary, when in fact it does not (message CPK521W). 2. A flag indicating that the extent is a user label extent (LABEL=(,SUL)) was found on, but the extent is not the first extent (message CPK521E). 3. Flags indicate extent is a shared (split) cylinder, not supported by z/OS or COMPAKTOR (message CPK521E). For problem (1), COMPAKTOR fixes the problem as long as the data set is moved or has free space released. For problems (2) and (3), list the VTOC as described under message CPK516E. Locate the DSCB in error and determine which problem it is, and superzap the bad DSCB to fix the problem. Contact INNOVATION DATA PROCESSING for assistance. DSCB AT CCHHR(HEX) -- cccchhhhrr -- HAS AN INVALID CHAIN POINTER OR COUNT FIELD Either the count field (hardware record ID) of the chain pointer (pointer to the next DSCB for this data set) was invalid. “cccchhhhrr” is the disk address of the DSCB (cylinder, track, and record, in hex). This can occur if: ❖ The count field of the specified DSCB does not match its physical location. ❖ ❖ The chain pointer in a Format 1 or 2 DSCB is invalid (does not point to a record in the VTOC). The chain pointer in a Format 3 DSCB is not zero for data sets that cannot exceed 16 extents. Use <strong>FDR</strong>DSF PRINT (see Section 20.5 “DSF PRINT Statement”) to print the track where the DSCB resides and determine what field is in error. If the count field is in error, you have a serious problem and should contact IBM. If the chain pointer in a Format 1 or 2 DSCB is invalid, you can attempt to superzap the DSCB. CPK523E DSCB AT CCHHR(HEX) -- cccchhhhrr -- HAS AN INVALID NUMBER OF EXTENTS Reason: The extent count in a Format 1 DSCB was invalid. “cccchhhhrr” is the disk address of the DSCB (cylinder, track, and record, in hex). This can occur if the extent count is greater that 128 for VSAM clusters and some SMS-Managed data sets, or greater than 16 for other data sets. Action: This is a serious problem. Determine the error type and attempt to fix the DSCB in error. CPK524E DSCB AT CCHHR(HEX) -- cccchhhhrr -- DESCRIBES AN EXTENT WHICH OVERLAPS SOME OTHER EXTENT. OVERLAPPING EXTENT'S LOW AND HIGH CCHH(HEX) -- cccchhhh-cccchhhh Reason: See associated CPK525E message. Action: See associated CPK525E message. CPK525E DSCB AT CCHHR(HEX) -- cccchhhhrr -- IS THE OTHER DSCB INVOLVED IN OVERLAP. OVERLAPPED EXTENT'S LOW AND HIGH CCHH(HEX) -- cccchhhh-cccchhhh Reason: COMPAKTOR has detected that two extent descriptor fields, in Format 1 or 3 DSCBs, claim ownership of the same track or tracks. This is a serious error. The data may be incorrect in either or both data sets. “cccchhhhrr” is the disk address of the DSCB (cylinder, track, and record, in hex). “cccchhhh” describes the overlapping extents (cylinder and track, in hex). Action: Determine the contents of the overlapped area and eliminate or fix one of the DSCBs involved. If one of the DSCBs is a Format 3 that has no F1/F2 pointing to it, then that is the one to be eliminated. Use SUPERZAP to zero out this DSCB (see message CPK516E).
CPK526E MESSAGES AND CODES COMPAKTOR MESSAGES (CPKNNNXX) 100.6 DSCB AT CCHHR(HEX) -- cccchhhhrr -- IS A SECOND FORMAT 4 DSCB Reason: Only one Format 4 DSCB is allowed in a valid VTOC. The identified DSCB is a second Format 4 DSCB. “cccchhhhrr” is the disk address of the DSCB (cylinder, track, and record, in hex). Action: This is a serious problem. SUPERZAP may be used to zero the invalid DSCB. Sample JCL to do this SUPERZAP is in member F4CLEAR in the <strong>FDR</strong> Installation Control Library (ICL). CPK527I THIS DATA SET WILL NOT BE RESTORED -- dsname Reason: An informative message from COMPAKT-from-backup. Used to provide a list of all data sets (such as temporary data sets) scratched by COMPAKTOR. CPK529I Reason: INDEXED VTOC EXISTS ON VOLUME=vvvvvv An active VTOC Index (SYS1.VTOCIX.volser) was detected on the volume. For SIM or MAP this is an informative message. On COMPAKT-from-backup, indicates that COMPAKTOR converts the volume to OS format prior to COMPAKTion. At the end of a successful COMPAKTion, COMPAKTOR reconverts back to an indexed VTOC by invoking ICKDSF. For a Fast COMPAKTion, the VTOCIX is updated directly with the new free space information. CPK530E CPKWORK MISSING INDEXED VTOC DISABLED Reason: For a COMPAKT-from-backup, COMPAKTOR found that the volume contained an active indexed VTOC but the CPKWORK DD statement was missing. COMPAKTOR converts the volume to OS VTOC format. Action: You must include a CPKWORK DD statement if COMPAKTOR is to convert the volume back to indexed format. You can execute the BUILDIX function of ICKDSF independently to convert back to an indexed VTOC. CPK531E IXSYSPRT DYNAMIC ALLOCATION FAILED INDEXED VTOC DISABLED Reason: COMPAKTOR attempts to allocate DDname IXSYSPRT to DUMMY so that ICKDSF can be invoked to rebuild the indexed VTOC. However, the dynamic allocation failed. Action: The IXSYSPRT DD statement could be included in the COMPAKTOR execution JCL to avoid the problem. For this volume, the user need simply execute the BUILDIX function of ICKDSF to rebuild the indexed VTOC since the COMPAKTion is completed. CPK532E ICKDSF ABNORMALLY TERMINATED WITH Ccccc Reason: COMPAKTOR invoked ICKDSF to rebuild the indexed VTOC. However, ICKDSF ended with a non-zero return code. Action: If a DD statement for IXSYSPRT to SYSOUT was included, examine the ICKDSF messages. If not, look up the ICKDSF return code “cccc” in ICKDSF documentation. If the error can be ignored, execute ICKDSF to rebuild the indexed VTOC. CPK533I INDEXED VTOC SUCCESSFULLY status Reason: There was an active Indexed VTOC (SYS1.VTOCIX.volser) on the volume being COMPAKTed. “status” can be: UPDATED – COMPAKTOR directly updated the free space maps in the Indexed VTOC. REBUILT – ICKDSF was successfully used to rebuild the indexed VTOC on the volume being COMPAKTed. CHAPTER 100 – PAGE 100-135 –
Page 1 and 2:
MESSAGES AND CODES INTRODUCTION TO
Page 3 and 4:
MESSAGES AND CODES FDR CONSOLE MESS
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
MESSAGES AND CODES MESSAGES FROM FD
Page 19 and 20:
FDR020 Reason: Action: MESSAGES AND
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
MESSAGES AND CODES CHAPTER 100 - PA
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
MESSAGES AND CODES CHAPTER 100 - PA
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84: MESSAGES AND CODES MESSAGES FROM FD
Page 85 and 86: MESSAGES AND CODES CHAPTER 100 - PA
Page 99 and 100: FDR547 Reason: Action: MESSAGES AND
Page 121 and 122: FDR939 Reason: MESSAGES AND CODES T
Page 123 and 124: MESSAGES AND CODES MESSAGES FROM SA
Page 125 and 126: 100.6 COMPAKTOR MESSAGES (CPKNNNXX)
Page 127 and 128: CHAPTER 100 - PAGE 100-127 - MESSAG
Page 129 and 130: MESSAGES AND CODES COMPAKTOR MESSAG
Page 133: MESSAGES AND CODES COMPAKTOR MESSAG
Page 145 and 146: MESSAGES AND CODES FDRREORG MESSAGE
Page 163 and 164: MESSAGES AND CODES ABEND CODES 100.
Page 169 and 170: 100.9 WAIT STATE CODES FROM SAR WAI
show all

FDR V54L78 - Innovation Data Processing

Create successful ePaper yourself

Delete template?

Save as template?