FDR V54L78 - Innovation Data Processing

MESSAGES AND CODES
COMPAKTOR MESSAGES (CPKNNNXX) 100.6
Action:
RECOVERY LOG FULL – The FASTCPK recovery log is full. More tracks were
moved than can be recorded in the recovery log. Remove operands that
cause many tracks to be moved (such as SIZEKEEP=0,
OBJECT=MINEXTS, DATA=ALL, and POS=) and rerun. Can occur if the
volume has few free space areas before COMPAKTion; you can add
CPKFREEX=nn to avoid COMPAKTing such volumes. FASTCPK will go
into recovery and return the volume to its previous state.
INSUFFICIENT FREE STORAGE TRACKS - VOLUME NOT CHANGED – There
are too few unallocated tracks on the volume for FASTCPK to successfully
operate. The U0888 ABEND can be suppressed for this “reason” by adding
UNABLE=IGNORE on the CPK statement.
NO FREE DSCB FOR RECOVERY LOG - VOLUME NOT CHANGED – There are
no free Format 0 DSCBs in the VTOC. FASTCPK requires at least one free
DSCB for its recovery log. The U0888 ABEND can be suppressed for this
“reason” by adding UNABLE=IGNORE on the CPK statement.
NO FREE TRACK FOR RECOVERY LOG - VOLUME NOT CHANGED – There is
no track on the volume that will be in free space both before and after the
FASTCPK. FASTCPK requires at least one such track for its recovery log.
The U0888 ABEND can be suppressed for this “reason” by adding
UNABLE=IGNORE on the CPK statement.
ALGORITHMS FAILED - VOLUME NOT CHANGED – None of the internal
repositioning algorithms used by COMPAKTOR was able to develop a new
layout for the volume. This usually occurs when you use POS= to position data
sets or have a large number of unmovable or active data sets and
COMPAKTOR was unable to find a location for a large data set. Reduce the
number of POS= operands and rerun. The U0888 ABEND can be suppressed
for this “reason” by adding UNABLE=IGNORE on the CPK statement.
INSUFFICIENT STORAGE - VOLUME NOT CHANGED – The region was insufficient
for FASTCPK. Increase the region size.
I/O ERROR - VOLUME NOT CHANGED – An I/O error occurred on the output
volume during initialization.
I/O ERROR WRITING RECOVERY LOG - VOLUME NOT CHANGED – An I/O error
occurred formatting the FASTCPK recovery log.
NON-STANDARD DATA SET NAME - VOLUME NOT CHANGED – The VTOC of
the volume contains a data set with a non-standard data set name, such as imbedded
blanks or non-standard characters. FASTCPK cannot handle such data sets.
An U0888 ABEND or non-zero return code will be issued at step end to call attention to
the error. Except for RECOVERY LOG FULL, the volume has not been changed; if
you can correct the error, rerun the job.
For RECOVERY LOG FULL, COMPAKTOR reverses the tracks already moved,
returning the volume to its original state. If the recovery fails, contact INNOVATION
DATA PROCESSING for assistance.
CPK555E VTOC TOO SMALL TO HOLD ALL DSCBS. INCREASE VTOC SIZE AND RETRY.
Reason: On a COMPAKT-from-backup, you changed the size of the VTOC (SELECT ***VTOC,SIZE=nnn),
but it is now too small for all the DSCBs that must be restored into it.
Action:
Reason:
Action:
Consult the summary map output by COMPAKTOR to determine the minimum VTOC
size you require. Correct control statement in error and rerun. Unless you are sure
that no new data sets are allocated on this volume, you should leave a generous
amount of free space in the VTOC.
VTOC SIZE OVERRIDE MUST BE RUN UNDER FDRPAS
VTOC SIZE OVERRIDE NOT SPECIFIED UNDER FDRPAS
The parameters passed to COMPAKTOR from the EXPANDVTOC keyword in FDRPAS
were overridden by the user.
Remove the COMPAKTOR overrides so the parameters specified by FDRPAS are used.
CHAPTER 100 – PAGE 100-138 –