FDR V54L78 - Innovation Data Processing

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 –