COMPAKTOR Messages (CPKnnnxx)

CPK301I

INNOVATION DATA PROCESSING -- COMPAKTOR VER v.r/mmt DATE yyyy.ddd TIME hh.mm.ss PAGE nnn

Explanation: General page header message for COMPAKTOR. See message FDR101 for details

CPK304I

PARM -- *parm-field data*

Explanation: Displays data input via the PARM= JCL operand on the EXEC statement.

CPK305I

CARD -- *control statement image*

Explanation: Displays all control statements input from SYSIN.

CPK306I

*** END OF CONTROL STATEMENTS. ***

Explanation: Indicates the end of input control statements.

CPK307I

NO CPK CONTROL STATEMENTS WERE FOUND.

Explanation: Neither the PARM= operand nor the SYSIN data set contained valid COMPAKTOR control statements.

COMPAKTOR RESTORED nnnnnnnn TRACKS

Explanation: “nnnnnnnn” is the actual number of tracks that COMPAKTOR wrote to the output volume. On Fast COMPAKTion or a COMPAKT-from-backup (DUMP=YES) to the original volume, this may be considerably less than the allocated tracks on the volume, since data sets that have not moved are not restored.

SIZEKEEP PERFORMANCE OPTION - nnnnnnnn TRKS KEPT FOR DSN AT RELATIVE STARTING TRK tttttttt

SIZEKEEP PERFORMANCE OPTION - nnnnnnnn TRKS KEPT TOTAL text

Explanation: The SIZEKEEP= operand was specified (or the default values from the FDR Global Options were used). The first form of the message is issued for each data set that was made unmovable by SIZEKEEP processing. You can identify the data set by looking up relative track “tttttttt” in the BEFORE or AFTER map. The second form of the message shows the total tracks that were made unmovable by SIZEKEEP. If SIZEKEEP is in effect but no “CPK319I” messages are printed, then SIZEKEEP was unable to meet the objective for the percent reduction in the free space areas without making all data sets movable.

COMPAKTOR OPTIONS IN EFFECT -- options

Explanation: Issued to inform you of run options in effect.

COMPAKTOR function STARTED

COMPAKTOR RECOVERY STARTED DUE TO FAILED COMPAKTION

Explanation: Issued just prior to start of DASD volume modification for RECOVERY, RELEASE, or RESTORE. If this message is not issued, the DASD volume was not altered in any way. After the message has been issued, the DASD volume being processed is unusable until message CPK322I is issued.

The second form of the message is issued when an FASTCPK fails and COMPAKTOR enters automatic recovery. It can also occur when COMPAKTOR discovers that a previous Fast COMPAKTION job did not complete, and did not perform automatic recovery.

COMPAKTOR function ENDED.

COMPAKTOR RECOVERY ENDED - DATA SETS RETURNED TO ORIGINAL LOCATIONS

COMPAKTOR RECOVERY ENDED - REORGANIZATION COMPLETE

Explanation: Indicates that COMPAKTOR has completed the operation RECOVERY, RELEASE, or RESTORE and the volume should be usable. Some cleanup operations (such as mapping the COMPAKTed volume and rebuilding the VTOC Index) may still remain to be done, so errors may still occur.

On a RESTORE from an FDR backup tape, if the text SOME BACKUP VOLUMES WERE NOT REQUIRED appears, this is simply an assurance that you need not be concerned if COMPAKTOR did not call for all the volumes of the FDR backup; tracks at the end of the volume did not need to be rewritten, probably because of %FOLD=nn or SIZEKEEP=.

The second form of the message is issued when COMPAKTOR RECOVERY has completed by backing out all changes and returning all data to its original location on the DASD.

The third form of the message is issued when COMPAKTOR RECOVERY was able to complete the original COMPAKTOR request and has moved all data to its intended location.

EXCESSIVE NUMBER OF DATA SET AND/OR DSGROUP NAMES INPUTTED

Explanation: Over 255 different names were found on SELECT control statements.

Action:  Rerun with fewer SELECT control statements.

CPK404W

operand=value IS INVALID. A DEFAULT VALUE MAY BE ASSUMED

Explanation: The “value” is invalid for the “operand”.

Action:  Check for valid data or numeric data for the keyword, as described in COMPAKTOR (CPK) - DASD Volume Reorganization. If COMPAKTOR abended, fix the invalid variable and rerun, otherwise check that the assumed default value is acceptable.

CPK405E

THE FROMDD= PARAMETER IS INVALID, OR ITS DD CARD IS MISSING, OR IT DOES NOT SPECIFY A type DEVICE, OR VOL= WAS SPECIFIED

Explanation: You specified FROMDD= but:

• The value was invalid.
• The ddname you specifies does not appear in the COMPAKTOR JCL.
• The device type allocated to the ddname is not TAPE or DISK.
• VOL= was also coded (you cannot use both).

Action:  Correct the error and rerun.

CPK406E

INVALID OR INCONSISTENT USE OF KEYWORD -- operand

Explanation: The operand “operand” is not valid for the form of the DSNAME statement you used, or conflicts with a mutually exclusive keyword that was also specified.

Action:  Correct the error and rerun.

CPK407E

LAST ’SEQ’ COMMAND SPECIFIED A NULL SET, OR THE ’ENDSEQ’ COMMAND IS NOT PRECEDED BY A ’SEQ’ COMMAND.

Explanation: No SELECT control statements were found between a SEQ and an ENDSEQ statement, or an ENDSEQ control statement is misplaced.

Action:  Correct error and rerun.

CPK408E

LAST READ CONTROL STATEMENT IS OUT-OF-SEQUENCE.

Explanation: A major statement is preceded by one or more minor statements, or a SELECT DSG= statement precedes a SELECT DSN/SEQ/ENDSEQ statement group.

Action:  Correct the error and rerun.

CPK409E

A REQUIRED OPERAND IS MISSING.

Explanation: An operand, either positional or keyword, required by the statement is missing.

Action:  Correct the error and rerun.

CPK410E

EITHER ’ENDSEQ’ COMMAND MISSING, OR POS=, DSG OR FILTER REQUESTED WITHIN A SEQUENCE SET. ASSUMING END OF SET

Explanation: 1. An ENDSEQ statement, delimiting a sequenced set, is missing.

2. A SELECT statement with a POS= or SCRATCH= operand was encountered within the range of a SEQ statement. You cannot code the POS= operand for individual members of a sequenced set.

3. A SELECT DSG= statement was encountered within the range of a SEQ statement.

Action:  An ENQSEQ statement is assumed before the incorrect statement. If this does not produce the correct results, correct the error and rerun.

CPK411E

THE FOLLOWING NAME WAS SPECIFIED MORE THAN ONCE -- dsn

Explanation: The data set name “dsn” was found on two or more SELECT statements. You may specify a particular data set name or data set name group only once.

Action:  Correct the error and rerun.

CPK412W

THE ’RLSE=’ OPERAND WILL NOT BE HONORED WHEN ’POS=KEEP’ IS ALSO SPECIFIED.

Explanation: Specifying POS=KEEP makes data sets unmovable, so their unused tracks cannot be freed.

Action:  None. This is only a warning message.

CPK413E

VTOC POSITIONING/SIZING IS INVALID WHEN ’VTOC=NOCHANGE’ OR %FOLD IS ALSO SPECIFIED.

Explanation: A SELECT ***VTOC statement was input to move and/or resize the VTOC, but VTOC=COMPAKT was not specified on the COMPAKT statement. It is also invalid if %FOLD= is specified.

Action:  Correct the error and rerun.

CPK425E

UNABLE TO PROCESS VOL=vol -- DUMMY VTOC OR CMS VOLUME

Explanation: COMPAKTOR found that the VTOC on volume “vol” started and ended on cylinder 0 head 0. This is the form of a dummy VTOC created on volumes formatted for VM.

Action:  The dummy VTOC does not contain any useful information, so COMPAKTOR bypasses this volume.

CPK426E

UNABLE TO OPEN DDNAME=ddn -- POSSIBLE MISSING DD CARD

Explanation: COMPAKTOR is unable to open for access the DD statement whose name is “ddn”. This usually occurs when the DD statement is missing.

Action:  Supply the appropriate DD statement and rerun.

CPK427E

CPK428E

CPK429E

CPK430E

THE DEVICE TO RESTORE TO -- devtype1 reason THE INPUT DEVICE -- devtype2

Explanation: When doing a COMPAKT-from-backup, and the output DASD (type “devtype1”) is not the same as the input DASD (“devtype2”) the DASD volumes are incompatible devices. “reason” may be:

IS INCOMPATIBLE WITH

The DASD volumes are different device types (for example, 3380 and 3390).

IS SMALLER THAN EAV

The DASD volumes are the same type, but the input is an EAV and the output is not. An EAV volume cannot be restored to a non-EAV volume.

IS SMALLER THAN

The DASD volumes are the same type but the output DASD is smaller than the input. This is a warning; as long as all the data fits on the output DASD and there are no unmovable data sets above the end of the output DASD, the run is successful.

Action:  Retry with a valid device as the target device.

CPK431E

CPK432E

‘SIZE=nnnnn’ IS TOO LARGE

Explanation: The specified new VTOC size “nnnnn” is excessively large.

Action:  Correct the error and rerun.

CPK433E

INVALID CCHH POSITION SPECIFIED -- ccccchhhh

Explanation: A POS= operand was specified with a track address but

• The cylinder address “ccccc” is invalid. It exceeds the device capacity.
• The track address “hhhh” is invalid. It exceeds the maximum number of tracks per cylinder.
• The given value is all zeros.

Action:  Correct the invalid address and rerun.

CPK451E

INVALID CONTINUATION OF A QUOTED STRING.

Explanation: A quoted string was improperly continued onto the following control statement. It does not start at column 16 of the continuation statement.

Action:  Correct the error and rerun.

CPK452E

EXPECTED CONTINUATION CARD NOT RECEIVED.

Explanation: Continuation was indicated on a control statement, but no further control statements followed.

Action:  Correct the error and rerun.

CPK453E

CONTINUATION COLUMN IS NON-BLANK, BUT LAST PARAMETER DOES NOT END WITH A COMMA OR IN COLUMN 071.

Explanation: See rules for Continuing an Operand Field in Control-Statement-Format.

Action:  Correct the error and rerun.

CPK454E

CPK455E

UNBALANCED PARENTHESES. EXPECTING A PARENTHESES AT COLUMN nnn

Explanation: A left (open) parenthesis does not have a matching right (close) parenthesis.

Action:  Correct the error and rerun.

CPK456E

INVALID USE OF DELIMITER AT COLUMN nnn

Explanation: A delimiter character (blank, parenthesis, apostrophe, comma, or equal sign) is used in violation of the COMPAKTOR statement language syntax.

Action:  Correct the error and rerun.

CPK457E

LAST READ CARD CONTAINED NO DATA.

Explanation: A completely blank control statement was input.

Action:  Correct the error and rerun.

CPK458E

UNIDENTIFIED COMMAND AT COLUMN nnn

Explanation: The statement starting at column “nnn” is not a valid COMPAKTOR statement.

Action:  Correct the error and rerun.

CPK459E

INVALID KEYWORD -- kkkkkkkk

Explanation: The keyword, “kkkkkkkk”, is not a valid keyword parameter for this statement.

Action:  Correct the error and rerun.

CPK460E

EXCESSIVE NUMBER OF OCCURRENCES OF COMMAND -- cccccccc

Explanation: The statement “cccccccc” has appeared more than its maximum number of occurrences. Check statement description in COMPAKTOR-CPK-DASD-Volume-Reorganization for the maximum allowed occurrences.

Action:  Correct the error and rerun.

CPK461E

UNIDENTIFIED POSITIONAL PARAMETER AT COLUMN nnn

Explanation: A positional parameter was detected starting at column “nnn”, but all positional parameters accepted by the statement have already been input.

Action:  Correct the error and rerun.

CPK462E

UNBALANCED APOSTROPHES. EXPECTING AN APOSTROPHE AT COLUMN nnn

Explanation: A quoted string does not begin and end with an apostrophe, an apostrophe is misplaced, or a single apostrophe within a quoted string is not correctly represented by two consecutive apostrophes.

Action:  Correct the error and rerun.

CPK463E

DUPLICATE KEYWORD DETECTED -- operand

Explanation: The “operand” appears more than once within the operand field of a particular statement.

Action:  Correct the error and rerun.

CPK464E

EXCESSIVE PARAMETER DATA LENGTH FOUND AT COLUMN nnn

Explanation: The variable data for a positional or keyword parameter exceeds its maximum allowed length.

Action:  Correct the error and rerun.

CPK465E

EXCESSIVE SUBPARAMETERS SPECIFIED STARTING AT COLUMN nnn

Explanation: Too many positional sub-operands, within parenthesis, were detected for a particular keyword or positional parameter.

Action:  Correct the error and rerun.

CPK470W

reason DSN=dsn

Explanation: The data set “dsn” was not moved. “reason” can be:

DATA SET IS ACTIVE OR UNMOVABLE

The data set is either in use by another task or is considered unmovable by COMPAKTOR (see Unmovable Data Sets in COMPAKTOR-Data-Set-Types).

DATA SET IS UNCHANGABLE

The extents of the data set cannot be combined (usually issued for a VSAM component whose characteristics inhibit combination).

DATA SET WAS NOT MOVED

The data set was not selected for movement. This message is printed only if the PRINT=ALL operand was specified.

DUPLICATE VVR EXISTS FOR

More than one VVR was detected in the VVDS for a given VSAM component.

CPK503E

CPK504E

INPUT TAPE IS NOT AN FDR DUMP TAPE

Explanation: While executing a COMPAKT-from-backup, either the input tape was not created by an FDR dump, or FDR encountered errors in the VTOC when dumping (message FDR125).

Action:  Insure tape is an FDR volume dump tape (DSF created tapes are not accepted by COMPAKTOR). Insure that tapes were mounted in the order they were created.

CPK505E

CPK506E

AUTHORIZATION CHECK FAILED

Explanation: The volume being COMPAKTed is defined to RACF with DASDVOL class protection, and the user id for this job does not have ALTER authority.

Action:  Authorize the user id to the volume, or run under an authorized user id.

CPK507E

INPUT TAPE HAS VTOC OR LABEL ERROR

Explanation: While executing a COMPAKT-from-backup, COMPAKTOR detected that the FDR backup does not contain a valid VTOC or a valid DASD volume label.

Action:  Use FDR to dump the volume again, and rerun COMPAKTOR.

CPK508E

CPK DOES NOT SUPPORT DUMPCOMPRESSEDTRACK (DCT) FORMAT OR ENCRYPTED TAPE. USE FDR RESTORE.

Explanation: While executing a COMPAKT-from-backup, COMPAKTOR detected that the FDR backup was created using:

• FDRCRYPT encryption.

Action:  COMPAKTOR cannot restore either of these formats.

• Rerun the backup without FDRCRYPT and rerun COMPAKTOR.
• Restore the backup with FDR and use FAST COMPAKTOR to do a COMPAKT-in-place.

CPK513E

INVALID REQUEST TO ELIMINATE UNUSED TRACKS FOR DATA SET- dsn.

DATA SET IS EITHER UNMOVABLE, UNCHANGEABLE, OR IS NOT A SEQUENTIAL OR PARTITIONED DATA SET.

Explanation: A SELECT statement specified “dsn” and requested that unused tracks or extents be freed. However, the data set is ineligible for this action.

Action:  Correct control statement in error and rerun.

CPK514W

POSSIBLE FORMAT 5 ERRORS IN VTOC.

Explanation: 1. Either no Format 5 DSCBs exist or they are incorrect.

2. The CONTAMINATION bit is on in the Format 4 DSCB, or the volume is a DOS (VSE) volume.

Action:  If COMPAKTing, none required since COMPAKTOR fixes this problem. If mapping or simulating, either fix the VTOC yourself, or COMPAKT the volume so that COMPAKTOR fixes it for you.

CPK515E

CPK517E

DATA SET NOT FOUND, OWNS NO EXTENTS, OR IS UNMOVABLE -- dsn

Explanation: Data set “dsn”, specified on a SELECT DSNAME statement, was not found, was a model DSCB (no space allocated), or was unmovable. See Unmovable Data Sets in COMPAKTOR-Data-Set-Types for a list of the types of data sets that COMPAKTOR considers to be unmovable.

Action:  Correct the error and rerun.

CPK518E

DSCB AT CCHHR(HEX) -- cccchhhhrr -- INVALID OR UNSUPPORTED DSCB TYPE t

Explanation: A DSCB was read and was not a Format 0, 1, 2, 3, 4, 5, 7, 8, or 9 DSCB. COMPAKTOR does not support Format 6 DSCBs that describe split cylinder data sets, no longer supported on z/OS.

Action:  If Format 6 DSCBs exist, you cannot COMPAKT, MAP, or SIMULATE this volume. You may want to list the VTOC as described under message CPK516E.

DSCB AT CCHHR(HEX) -- cccchhhhrr -- HAS AN INVALID EXTENT ADDRESS addr -- DATA SET-dsn

Explanation: One or more extent descriptions in a DSCB are invalid. “cccchhhhrr” is the DASD address of the DSCB (cylinder, track, and record, in hex). “addr” is the invalid extent address, and “dsn” is the name of the data set associated with this DSCB. This can occur if:

• An extent descriptor is all zeros.
• The starting address of the extent is less than the ending address.
• For an SUL (standard user label) data set, the first extent is not exactly one (1) track.
• The starting or ending cylinder number is greater than the number of cylinders on the volume. This may occur if COMPAKTOR cannot properly identify the type or capacity of the DASD.

A DSN IN TRACK nnnnn OF THE VTOC HAS AN INVALID EXTENT

Explanation: This form of the CPK519E message shows the track number “nnnnn” in the VTOC that contains invalid DSCB information. This can occur if:

• The number of extents in the Format 1 exceed the actual number of extents.
• The Format 3 in the DSCB chain has fewer extents than are defined in the Format 1.

Action:  This is a serious error and should be attended to immediately. Follow procedures described in COMPAKTOR-VTOC-Errors.

This error can also occur if the volume has been initialized with an incorrect number of data cylinders or alternate tracks and the data set is at or near the end of the volume. If you also receive message CPK512I, correct the error as described under that message and rerun COMPAKTOR to see if the CPK519E message still occurs.

CPK520W

DSCB AT CCHHR(HEX) -- cccchhhhrr -- HAS AN INVALID EXTENT SEQUENCE NO.

Explanation: Extents owned by a data set are numbered from 0 to 127, ascending. A violation of this rule was detected.

Action:  See message CPK519E.

CPK521x

CPK522E

DSCB AT CCHHR(HEX) -- cccchhhhrr -- HAS AN INVALID CHAIN POINTER OR COUNT FIELD

Explanation: 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 DASD 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.

Action:  Use FDRDSF PRINT (see 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

Explanation: The extent count in a Format 1 DSCB was invalid. “cccchhhhrr” is the DASD 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

Explanation: See associated CPK525E message.

Action:  See associated CPK525E message.

DSCB AT CCHHR(HEX) -- cccchhhhrr -- IS THE OTHER DSCB INVOLVED IN OVERLAP.

OVERLAPPED EXTENT'S LOW AND HIGH CCHH(HEX) -- cccchhhh-cccchhhh

Explanation: 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 DASD 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

DSCB AT CCHHR(HEX) -- cccchhhhrr -- IS A SECOND FORMAT 4 DSCB

Explanation: Only one Format 4 DSCB is allowed in a valid VTOC. The identified DSCB is a second Format 4 DSCB. “cccchhhhrr” is the DASD 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 FDR Installation Control Library (ICL).

CPK527I

THIS DATA SET WILL NOT BE RESTORED -- dsn

Explanation: 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

INDEXED VTOC EXISTS ON VOLUME=vol

Explanation: 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

Explanation: 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

Explanation: 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.

Explanation: 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

Explanation: 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.

CPK534E

CPK535W

CPK CANNOT REBUILD THE INDEXED VTOC - USER MUST REBUILD IT USING ICKDSF

Explanation: The volume serial of the COMPAKTed volume duplicates that of another online volume, and COMPAKTOR has placed it offline.

Action:  Once you can bring the volume online (perhaps after varying the original volume offline), execute the BUILDIX function of ICKDSF to rebuild the VTOC index.

VOLUME=vol IS A SYSTEM MANAGED VOLUME-- [IN INITIAL STATUS]

Explanation: The VTOC of the DASD volume “vol” indicates that it is in System Managed Storage (SMS) format. If “IN INITIAL STATUS” appears, the volume is not yet completely converted to SMS.

CPK537E

HOWEVER THE UCB DOES NOT INDICATE SMS

Explanation: This appears after message CPK536I to indicate that the UCB of the input DASD does not also indicate that it is SMS-managed. This may occur if the SMS-managed volume is being accessed from a system that does not have SMS installed or active, or if the volume is not currently defined to SMS as a member of a Storage Group.

Action:  None. COMPAKTOR continues, unless message CPK538E is issued. However, if this system does have SMS active, it may indicate a problem with the SMS status of this volume.

WARNING - OUTPUT VOLUME IS NOT SMS COMPATIBLE - VOLUME BYPASSED

Explanation: The System Managed Storage (SMS) status indicated in the VTOC of the input volume (SMS-managed or not managed) does not match the SMS status indicated in the UCB of the output DASD. You can SIMULATE the COMPAKTion, but any other function gets the text VOLUME BYPASSED and the COMPAKTion is not done (unless SMSPROT=NONE is specified).

Action:  Ensure that the output DASD has the same SMS-managed status as the input DASD volume or FDR backup. If you want to do the COMPAKTion in spite of this error (for example, when moving or restoring SMS-managed volumes on a non SMS system), specify the operand SMSPROT=NONE on the COMPAKT statement.

CPK540W

FORMAT n DSCB AT CCHHR(HEX) -- cccchhhhrr -- DEFINES AN INVALID FREE AREA IN EXTENT DESCRIPTOR nn

Explanation: A free extent descriptor in a Format 5 or Format 7 DSCB is invalid. “cccchhhhrr” is the DASD address of the DSCB (cylinder, track, and record, in hex). “nn” identifies the descriptor within that DSCB (the nn ^th  extent descriptor). This can occur if the extent values are invalid (for example, point to tracks beyond the end of the volume) or point to tracks that are currently allocated to a data set.

Action:  If you are actually COMPAKTing the volume, COMPAKTOR automatically creates accurate Format 5/7 DSCBs.

CPK541W

FORMAT n DSCBS LEAVE nnnnnnnn TRACKS UNACCOUNTED FOR

Explanation: Some tracks are not allocated to any data set and are not described by any Format 5 or Format 7 DSCB.

Action:  If you are actually COMPAKTing the volume, COMPAKTOR automatically creates accurate Format 5/7 DSCBs.

UNABLE TO HONOR REQUEST TO ALTER VTOC POSITION OR SIZE. VSAM DATA SETS EXIST ON VOLUME

Explanation: A SELECT ***VTOC statement was input but non-ICF VSAM clusters with non-zero secondary allocation quantities exist on volume to be COMPAKTed.

Action:  Remove the SELECT statement; or, if you need to alter the size or location of the VTOC on this volume, you must first EXPORT all objects in VSAM data spaces with non-zero secondary allocation quantities, and DELETE the data spaces. After COMPAKTion, you can IMPORT the objects.

CPK543W

INVALID REQUEST TO CHANGE VTOC POSITION OR SIZE. VSAM DATA SETS EXIST ON VOLUME. SIMULATION WILL CONTINUE

Explanation: A SELECT ***VTOC statement was input but non-ICF VSAM clusters with non-zero secondary allocation quantities exist on source volume.

Action:  COMPAKTOR continues the simulation and performs any requested VTOC position or size changes. However, this message is to warn you that your request to alter the VTOC’s position or size is not honored during a real COMPAKTion (message CPK542E).

CPK552E

THE FOLLOWING DATA SET IS INELIGIBLE FOR POSITIONING -- dsn

IT IS EITHER UNMOVABLE, HAS A STANDARD-USER LABEL, OR GIVEN CCHH POSITION IS INVALID FOR THIS DATA SET.

Explanation: The data set “dsn” was named on a SELECT statement with POS= specified or included in a sequence set with POS=. The positioning requested is not possible because:

• 
  
  • It is marked as unmovable.
  • It has a user labels (LABEL=(,SUL)).
  • It must be on a cylinder boundary but the given position is not on such a boundary.
  • It was positioned so that, while its first track was within the capacity of the volume, one or more tracks at the end of the data set were outside the volume track boundaries.

Action:  Correct the error and rerun.

CPK553E

ONE OR MORE ABSOLUTE POSITIONED OR ACTIVE DATA SETS OR VTOCSIZE OVERLAP A DATA SET AT CCCC.CCCH(HEX) -- ccccc.ccch

Explanation: One or more SELECT or SEQ statements requested absolute positioning for data sets (POS=) but it could not be honored because:

• 
  
  • A data set would overlap an unmovable or previously positioned data set.
  • If the cylinder/head address is beyond the end of the volume, then a data set or a sequenced set of data sets was positioned so that its end was outside the boundaries of the volume.

“cccc.ccch” is the cylinder and track numbers (in hex) of the data set that would be overlapped.

Action:  Consult the extents map produced by COMPAKTOR and fix your control statements

CPK555E

VTOC TOO SMALL TO HOLD ALL DSCBS. INCREASE VTOC SIZE AND RETRY.

CPK532E

ICKDSF ABNORMALLY TERMINATED WITH Ccccc

Explanation: 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:  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

Explanation: The parameters passed to COMPAKTOR from the EXPANDVTOC keyword in FDRPAS were overridden by the user.

Action:  Remove the COMPAKTOR overrides so the parameters specified by FDRPAS are used.

VTOC SIZE OVERRIDE IGNORED - NOT LARGER THAN nnnnnn TRACKS

Explanation: The parameters passed to COMPAKTOR from the EXPANDVTOC keyword in FDRPAS were too small.

Action:  Increase the number of tracks to expand the VTOC.

UNABLE TO IMPROVE VOLUME BY function

Explanation: COMPAKTOR cannot improve the volume by COMPAKTING or RELEASE. Perhaps it was recently COMPAKTed. For TYPE=RLSE, no space could be released.

Action:  An U0888 abend or non-zero return code may be issued at step end to call attention to the warning; if you do not want the abend/code, specify UNABLE=IGNORE on the CPK statement. Since no changes have been made to the volume, COMPAKTOR does not produce the “after” map. If COMPAKTing, the volume is not COMPAKTed, but a SIMULATION is done instead. If you wish to force COMPAKTOR to COMPAKT the volume specify any positioning statement.

CPK557E

UNABLE TO ALLOCATE SEQUENCED SET CONTAINING DATA SET -- dsname

THE SEQUENCED SET IS PROBABLY TOO LARGE.

Explanation: After allocating all unmovable data sets and the VTOC, COMPAKTOR tried to allocate space for the sequenced set containing the named data set. It was unable to do this, because it could not find a single contiguous area large enough to hold the entire sequenced set.

Action:  Remove some data sets from the sequenced set and rerun.

CPK558I

COMPAKTOR WILL NOW DO AN FDR RESTORE OF THE VOLUME.

Explanation: COMPAKTOR restores the volume.

CPK559W

function BYPASSED DUE TO VOLUME reason

Explanation:  COMPAKTION, RELEASE, or SIMULATION was bypassed on this volume because:

NOT EXCEEDING CONDITIONAL COMPAKTION OPTIONS

One or more of the operands CPKFREEX, CPKDSNMX, CPKMULTX, or MINRLSE were specified, but none of the specified values were exceeded on the volume.

BEING EXCLUDED

The volume was named in an EXCLUDE entry in the COMPAKTOR Unmovable Table.

Action:  The volume is not COMPAKTed.

CPK560W

CPK DID NOT FIND REQUESTED VOL/STORGRP=xxxxxxxx

Explanation: The VOL= or STORGRP= operands were specified, requesting dynamic allocation of the volume or SMS storage groups named. Either the storage group is not defined to SMS, or the volumes in the storage group or the volumes specified by VOL= were not mounted on any online DASD device.

Action:  COMPAKTOR proceeds to the next requested volume, if any. If the volume serial or storage group name was misspelled or inaccurate, correct it and rerun COMPAKTOR. However, after processing all properly specified volumes, COMPAKTOR ends with an error U0888 unless SELTERR=NO was coded.

CPK561E

DISK DYNAMIC ALLOCATION ERROR VOL=vol UNIT=unit COMP=comp CODE=code

Explanation: A dynamic allocation of DASD volume “vol” on device “unit” failed with completion code “comp” and reason code “code”. These codes are documented in the IBM manual Authorized Assembler Services Guide. They can also be found in Appendix A of the ISPF online HELP.

Action:  COMPAKTOR proceeds to the next requested volume, if any.

CPK562I

COMPAKTOR PROCESSING NEXT -- options

Explanation: 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

Explanation: 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 DASD.

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

COMPAKTOR WILL RELEASE nnnnnnn TRACKS -- LEAVING mmmmmmm TRACKS DSN=dsn

COMPAKTOR WILL RELEASE nnnnnnnnn TRACKS FROM VOL=vol

Explanation: For TYPE=RLSE only, the first format lists the number of tracks “nnnnnnn” to be released from the data set “dsn” (leaving “mmmmmmm” tracks allocated to the data set). The second format indicates the total tracks “nnnnnnnnn” to be released on volume “vol”.

CPK581E

TRACK tttttt WAS NOT RESTORED.

Explanation: 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

Explanation: COMPAKTOR had an error processing or updating the VVDS on the volume being COMPAKTed. “ccccc hhhh rr” is the cylinder, head, and 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.

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).

Action:  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

Explanation: 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

VOL=vol IS IN RECOVERY DUE TO A FAILED COMPAKTION AT hh.mm ON yy.ddd

Explanation: A Fast COMPAKTion (CPK TYPE=FASTCPK) on volume “vol” 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.

CPK587W

CPK595E

CPK600In

COMPAKTOR status type RUN -- VOL=vol

Explanation: Informs you of the status of the run. “type” is the type of run: MAPPING, SIMULATION, RELEASE, or COMPAKTION. “status” is SUCCESSFULLY COMPLETED or COMPLETED WITH ERRORS; in the latter case, some warning messages were issued but the COMPAKTion was able to complete. “n” is an internal code indicating the volume reorganization algorithm was used to position the data sets.

CPK601I

RESTORED DEVICE IS UNIT=unit,VOLSER=vol,DEVTYPE=ddddddd

Explanation: Identifies the COMPAKTed volume if an output DASD was modified.

CPK602A

SERIOUS ERRORS DETECTED. COMPAKTOR ABENDING

Explanation: One or more previous error messages were issued and COMPAKTOR terminates abnormally.

Action:  See the Action for the other error messages.

CPK603A

COMPAKTOR RESTORE CANCELLED reason

Explanation: The COMPAKTion of the current volume was bypassed because:

SYSTEM RESIDENCE VOLUME

You cannot COMPAKT the current SYSRES volume (IPL volume).

BY CONSOLE OPERATOR

The operator replied “NO” to the FDRW80 WTOR message.

CPK604W

COMPAKTOR OPERATION TERMINATED BY CANCEL COMMAND -- REMAINING VOLUMES BYPASSED

Explanation: The operator attempted to cancel the COMPAKTOR job and it was intercepted by COMPAKTOR CANCEL protection. The operator then replied “S” to the FDRW99 message, causing COMPAKTOR to terminate after completing processing on the current volume. If more volumes were to be processed in the step, they are bypassed.

CPK605W

COMPAKTOR ABENDING DUE TO EXCEEDING MAXIO

Explanation: COMPAKTOR terminates due to exceeding MAXIO.

CPK606E

CPK607E

SENSE ERROR - UNKNOWN DEVICE OR DEVICE NOT ECAM CAPABLE

SENSE=<32 bytes of sense data in hex>

Explanation: FAST COMPAKTOR was executed with SNAPSHOT=YES, but the current installed microcode does not support the ECAM commands required for SnapShot, probably because it was not an IBM RVA or Oracle StorageTek DASD subsystem. This message is just informational; it is not normally printed unless a debugging option is enabled.

Action:  The volume is COMPAKTed with normal READ and WRITE CCWs.

CPK608E

CPK609E