FDR V54L78 - Innovation Data Processing

More documents

Recommendations

Info

CPK562I Reason: CHAPTER 100 – PAGE 100-140 – MESSAGES AND CODES COMPAKTOR MESSAGES (CPKNNNXX) 100.6 COMPAKTOR PROCESSING NEXT -- options Processing of more than one volume was requested by the VOL= or STORGRP= operands. This message appears instead of CPK320I for the second and subsequent volumes. CPK563E operand INVALID REASON = reason Reason: The VOL or STORGRP operand was specified, but it is invalid for the reason indicated, which may include: CANNOT BE SPECIFIED UNDER FDR/ABR – Not valid when COMPAKTOR is invoked by FDR or FDRABR. ONLY ONE VOLUME CAN BE SPECIFIED ON CPK TYPE=COMPAKT – NO VOLUMES FOUND TO BE ONLINE – Volumes specified are not mounted on any online disk. DISK1 DD STATEMENT SPECIFIED – Cannot be used if a DISK1 DD statement is also provided. Action: If possible, correct the error and re-execute COMPAKTOR. CPK564I Reason: COMPAKTOR WILL RELEASE nnnnnnn TRACKS -- LEAVING mmmmmmm TRACKS DSN=dsname COMPAKTOR WILL RELEASE nnnnnnnnn TRACKS FROM VOL=vvvvvv For TYPE=RLSE only, the first format lists the number of tracks “nnnnnnn” to be released from the data set “dsname” (leaving “mmmmmmm” tracks allocated to the data set). The second format indicates the total tracks “nnnnnnnnn” to be released on volume “vvvvvv”. CPK581E ANOMALOUS DATA ON TAPE WHOSE DD-NAME IS dddddddd Reason: During a COMPAKT-from-backup, this error may be caused by a number of internal consistency checks of the data read from an FDR backup. Action: Contact INNOVATION DATA PROCESSING for assistance. CPK582E TRACK tttttt WAS NOT RESTORED. Reason: I/O errors forced COMPAKTOR to skip certain DASD tracks and/or tape blocks during the restore. Usually proceeded by one or more CPK501E and/or CPK502E messages. Action: “tttttt” is the track number, relative to zero, of the track not restored. To determine which data set owns this track, you must locate the track in the BEFORE COMPAKTion map. Either recreate the data set, or retry the COMPAKTion using different DASD or tape devices. CPK583E ERROR action VVDS DATA SET CCHHR=ccccc hhhh rr REASON=n Reason: COMPAKTOR had an error processing or updating the VVDS on the volume being COMPAKTed. “ccccc hhhh rr” is the cylinder/head/record (in decimal) of the VVDS block causing the error. “n” is a reason code: 1 – VVDS block is invalidly formatted. 2 – VVDS block length is invalid. 3 – I/O error reading the VVDS. 4 – Unable to acquire storage to save the VVDS. 5/6 – Error accessing the VDSAB (pointer to the VVDS). A – VVR record type is invalid. B – Type 23 cell is missing from VVR. C – Extent number is zero in type 23 cell. D – Tracks/extent is not a multiple of CASIZE. E – Bytes/extent is not a multiple of CAs/extent. F – Extent exceeds volume size. G – HI-ALLOC-RBA invalid.
MESSAGES AND CODES COMPAKTOR MESSAGES (CPKNNNXX) 100.6 Action: H – Extent Count has increased. J – Extent Count in Type 60 cell is invalid. K – Extent Count in Q record invalid. L – Duplicate Type Q record (imbedded index). Numeric reason codes cause the whole VVDS block to be bypassed; some clusters may not be updated correctly. Alphabetic codes cause the VVR to be bypassed; only the cluster in that VVR is affected. You should run an IDCAMS DIAGNOSE on the VVDS when any of these errors occur to identify errors in the VVDS. If DIAGNOSE indicates that the VVR only exists in the VVDS and not in the VTOC, then run an IDCAMS DELETE VVR to remove the orphan VVR entry from the VVDS. If the message contains an alphabetic reason code and the component does exist on the volume, run an IDCAMS REPRO to backup the cluster, next DELETE the cluster, and then re- DEFINE the cluster and finally REPRO the data back into the cluster. An IDCAMS EXPORT with PERMANENT followed by an IMPORT can also accomplish the same results as the REPRO / DELETE / re-DEFINE / REPRO. CPK584E ERROR UPDATING VVR COMP=ssss CODE=uuuu DSN=component Reason: COMPAKTOR was updating the VVDS on another volume because a multi-volume cluster with a piece on this volume was changed, and an error occurred. The CPL (Catalog Parameter List) that failed is printed following the message. For COMP values less than 4000, “ssss” is the return code and “uuuu” is the reason code as defined under message IDC3009I in the appropriate IBM messages Manual. “ssss” values over 4000 are generated by COMPAKTOR: 4089 – HI-ALLOC-RBA has gone negative. 4090 – HI-ALLOC-RBA is not a multiple of CISIZE. 4091 – HI-ALLOC-RBA was not returned. 4092 – AMDSBCAT address was not returned. 4093 – Type 23 cell track count went negative on the volume being COMPAKTed. 4094 – Type 23 cell extent count went negative on the volume being COMPAKTed. 4095 – Type 60 cell extent count went negative. Action: The VVR is bypassed. This probably indicates an error in the VVR, such as duplicate or orphan VVRs. You should run an IDCAMS DIAGNOSE on each VVDS involved. CPK585E UNABLE TO MOVE CCHH=X'cccchhhh' reason Reason: FAST COMPAKTion was unable to move track “cccchhhh”. Action: This is an internal error. Contact INNOVATION DATA PROCESSING. CPK586W VOL=vvvvvv IS IN RECOVERY DUE TO A FAILED COMPAKTION AT hh.mm ON yy.ddd Reason: A Fast COMPAKTion (CPK TYPE=FASTCPK) on volume “vvvvvv” started at the indicated time (“hh.mm”) and date (“yy.ddd”) but that COMPAKTion did not complete for some reason, such as a system crash. This message is subsequently produced by any COMPAKTOR function against the failed volume, including MAP. The volume is not in a usable status; many data sets are not usable until COMPAKTOR recovery is completed. Action: The Fast COMPAKTion must be restarted so that it can recover and make the volume usable again. If the COMPAKTOR step getting the CPK586W message is a Fast COMPAKTion, COMPAKTOR automatically does this recovery, after asking permission from the operator via an FDRW80 message (specify RECOVERY=YES on the CPK statement if you want to bypass the WTOR and immediately proceed with the recovery). If this is a MAP or SIM, the step proceeds but gets an U0888 ABEND at the end. If it is a CPK TYPE=CPK (COMPAKT from backup), it is terminated immediately. In either case, you must submit a Fast COMPAKTion against this volume to make it usable by returning all data tracks to their original locations. CHAPTER 100 – PAGE 100-141 –
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:
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:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90: MESSAGES AND CODES MESSAGES FROM FD
Page 95 and 96: 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 135 and 136: CPK526E MESSAGES AND CODES COMPAKTO
Page 139: 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?