Messages CTT200 through CTT2xx

This group includes messages for the Control-M/Tape product.

CTT200S operation FAILED FOR logical_ds DATASET. RC= rc, REASON= ic_rsn

Explanation: The specified operation against the logical data set logical_ds failed.

Valid values for logical_ds are shown in the following table:

logical_ds	Description
MDBD	Media database data file
MDBI	Media database index file
STKD	Stacking database data file
STKI	Stacking database index file
TRACE	Trace file
SEQ	Any sequential file

The reason for the failure is indicated by ic_rsn, where ic is a 2-digit internal code, and rsn is the 4-digit reason code described in the following tables.

Logical Errors in Database Data File and Database Index Files

rsn	Description
0004	READ - key not found READNEXT - end of file reached READPREV - beginning of file reached
0008	Non-unique key (add)
0012	Invalid function
0016	Invalid record has been read or supplied
0020	Not enough memory
0024	Not enough storage in data file
0028	Not enough storage in index file
0030	Internal error: no message retriever found
0032	Missing parameters
0036	Invalid record type
0044	Invalid LRECL in data file
0048	Invalid KEYLEN in index file
0052	Simulation failed, restart
0056	Open for Trace file failed
0060	TCT address invalid (open)
0066	Invalid key change during update

Errors in Database DATA File

rsn	Description
1004	ADD - the file is full READNEXT - no more records READPREV - beginning of file reached
1006	Record not found
1008	Record not found--invalid extent number
1009	Record not found--invalid block number
1010	Internal error: Record not found--invalid extent number
1011	Internal error: Record not found--invalid block number
1012	Insufficient memory
1013	Open failed for the DD statement name
1016	The free record counter in the database is corrupt.
1018	Corrupted record
1019	Record is not active
1020	Invalid QNAME (open)
1021	Bad record in free list
1022	Invalid data set name in block 0
1024	Invalid function
1028	Load of IOAPARM failed
1032	Add failed, record too long
1036	I/O error
1044	EXCP initialization error
1046	Dual database file corrupted--not up to date, aborting
1048	Invalid data set name, or data set name too long
1050	Locate failed
1052	Dynamic allocation failed
1054	Dynamic allocation free failed
1056	Dual database file not up to date
1058	Dual database file corrupted--continue working with main database
1060	Failed to link IOADBF
1064	Failed to format new database file
1066	Cannot update block 0--block was not ENQed
1068	Update failed--record too long
1070	Failed to load IOADBSB#
1072	Cannot perform read with ENQ--another ENQ was already issued
1074	Cannot open database exclusively--database is in use
1076	Failed to update block 0--corrupted data
1078	Failed to update block 0--dual database flags changed without appropriate ENQ
1080	Buffering not initialized
1082	ENQ failed
1084	Compress/uncompress error
1086	Internal error--current EFCB does not match the RBA to be written
1090	Attempted to update database while it was open for read-only
1092	Open failed: read job file control block failed for the DD statement name.

Logical Errors in Database Index File

rsn	Description
2004	ADD - key already exists DELETE - record not found READ - record not found READNEXT - end of file reached READPREV - beginning of file reached
2008	Error accessing the file
2012	Not enough main storage
2016	Internal error
2018	The index tree structure is corrupted--an index on a higher level does not match the last index on a lower level.
2019	The index tree structure is corrupted--index was not found on the block.
2020	Invalid index function
2024	Invalid timestamp
2028	Invalid chain

Data Errors in Database Index File

rsn	Description
3004	ADD - file is full READNEXT - no more records READPREV - beginning of file reached
3006	Record not found
3008	Record not found--invalid extent number
3009	Record not found--invalid block number
3010	Internal error: Record not found--invalid extent number
3011	Internal error: Record not found--invalid block number
3012	Not enough memory
3013	Open failed for DD name
3016	The free record counter in the database is corrupt.
3018	Corrupted record
3019	Record is not active
3020	Invalid QNAME (open)
3021	Bad record in free list
3022	Invalid data set name in n block 0
3024	Invalid function
3028	Failed to load IOAPARM
3032	Add failed--record too long
3036	I/O error
3044	EXCP initialization error
3046	Dual database file corrupted--not up to date, aborting
3048	Invalid data set name, or data set name too long
3050	Locate failed
3052	Dynamic allocation failed
3054	Dynamic allocation free failed
3056	Dual database file not up to date
3058	Dual database file corrupted--continue working with main database
3060	Failed to link IOADBF
3064	Failed to format new database file
3066	Cannot update block 0--block was not ENQed
3068	Update failed--record too long
3070	Failed to load IOADBSB#
3072	Cannot perform read with ENQ--another ENQ was already issued
3074	Cannot open database exclusively--database is in use
3076	Failed to update block 0--corrupted data
3078	Failed to update block 0--dual database flags changed without appropriate ENQ
3080	Buffering not initialized
3082	ENQ failed
3084	Compress/uncompress error
3086	Internal error--current EFCB does not match the RBA to be written
3090	Attempted to update database while it was open for read-only
3092	Open failed: read job file control block failed for the DD statement name.

Errors in TRACE or SEQ Files

rsn	Explanation	Description
4004	READ	Record truncated because it was too long
	READ0	Record truncated because it was too long
4008	OPEN	Not enough memory
	READ	Record or block could not be read
	READ0	Record or block could not be read
	WRITE	Record or block could not be read
4012	OPEN	OPEN failed, or JFCB could not be obtained
	READ	Invalid RBA or EOF
	READ0	Invalid RBA or EOF
	WRITE	Record could not be written
	WRITE0	Record could not be written
4016	OPEN	Internal error--IOADBE initialization failed
	READ	Sequence error
	READ0	Sequence error
	WRITE	Sequence error
	WRITE0	Sequence error
4020	OPEN	Error reading record 0
	WRITE	Trace file is full
4024	OPEN	Trace file format is invalid
4028	OPEN	Trace file is full
4032	Internal error--invalid function for all TRACE or SEQ file operations.

Errors during sequential read of Media database

rsn	Description
5002	End of physical file (extent)
5004	End of file
5008	The file could not be opened. RDJFCB failed (probably no DD statement for the MDB).
5012	The file could not be opened. OPEN for MDB failed.
5016	Invalid dsname specified in DD statement referencing the MDB. Either name is too long or the name does not end with E000.
5020	Parameters error
5024	File attributes incorrect. File type incorrect.
5028	File attributes incorrect. Lrecl incorrect.
5032	File attributes incorrect. Blksize incorrect.
5036	File attributes incorrect. Dsname incorrect.

The currently executing function or utility stops.

Corrective Action: Notify your INCONTROL administrator.

CTT202I RECORD: key

Explanation: This information message follows another error message, and identifies the Media Database (MDB) record for which the operation identified in the earlier message failed.

Corrective Action: No action is required.

CTT203E CTTAPI FAILED. FUNCTION= func RC= rc RSN= rsn URC= urc

Explanation: The Control-M/Tape Application Program Interface (CTTAPI) has failed to perform one of its functions.

The variables in this message are:

func - the function that was not performed
rc - the return code
rsn - the reason code
urc - the utility return code, if a utility was run

The following table displays valid values for the return code and reason code, together with the relevant explanations:

Return Code	Reason Code	Explanation
8	200	No handler sent
8	204	GETMAIN failed
	208	No active query when query next
	212	Invalid call - invalid eye catcher
	216	No buffer when query
	220	Subtask error
	224	Open error from database. To identify the error that has occurred, use the value of urc as if it was the reason code in the CTT200S message.
	228	Close error from database. To identify the error that has occurred, use the value of urc as if it was the reason code in the CTT200S message.
	232	Load environment error
	236	Control-M/Tape real time environment is not active
	240	Allocate database error
	244	Free database error
	248	User not authorized
	252	Expiration management error
	256	MDB was not opened in update mode
	260	The program is not APF-authorized.
12	200	Function is not supported
	204	Path is invalid
	208	Relation is invalid
	212	Relation is inconsistent
	216	Mask is invalid
	220	Parsing error
	224	Invalid combination of where and path
	228	INCLUDE or EXCLUDE error
	232	Invalid options have been specified.
	236	A non-existent volume has been specified.
	240	The specified data set does not exist.
	244	The data set name specified does not match an actual data set name.
	248	The request is inconsistent with the current environment. An External Data Manager (EDM) attempted to mark as expired a volume not marked as under the control of that EDM.
16	200	Dynamic allocation error
	204	Dynamic free error
	208	Read error from database. To identify the error that has occurred, use the value of urc as if it was the reason code in the CTT200S message.
	212	Sort error
	216	More than two API parallel query tasks are not allowed.

Corrective Action: Use the information in this and any associated message to identify the problem, and take action accordingly.

CTT204W NUMBER OF FREE RECORDS IN file BELOW THRESHOLD

Explanation: The number of free records in the specified file has fallen below the installation default. The file indicated in this message is either MDB (the Media Database) or STK (the Stacking Database). This message is issued each time a record is added to the specified file while the situation persists.

Corrective Action: The size of the specified file should be examined and enlarged according to the current needs of the site. Refer to the INCONTROL for z/OS Administrator Guide.

CTT205S {MDB | STK} DATA FILE IS FULL

Explanation: An attempt was made to add a new record to the Media Database (MDB) or Stacking Statistic Database (STK), but the MDB/STK Data file has no free space left.

Processing stops.

Corrective Action: The MDB/STK Data file should be enlarged. Refer to the INCONTROL for z/OS Administrator Guide.

CTT206S {MDB | STK} INDEX FILE IS FULL

Explanation: An attempt was made to add a new record to the Media Database (MDB) or Stacking Statistic Database, but the MDB/STK Index file has no free space left.

Processing stops.

Corrective Action: The MDB/STK Index file should be enlarged. Refer to the INCONTROL for z/OS Administrator Guide.

CTT207S DATA FILE FORMATTED INCORRECTLY

Explanation: The format of the Media Database (MDB) Data file is incorrect. This message indicates that the LRECL of the Data file is not correct.

Processing stops.

Corrective Action: Refer to the Control-M/Tape chapter in the INCONTROL for z/OS Installation Guide and run the CTTDBF utility to format the MDB correctly.

CTT208S INDEX FILE FORMATTED INCORRECTLY

Explanation: The format of the Media Database (MDB) Index file is incorrect. This message indicates that the KEYLEN of the Index file is not correct.

Processing stops.

Corrective Action: Refer to Control-M/Tape chapter in the INCONTROL for z/OS Installation Guide and run the CTTDBF utility to format the MDB correctly.

CTT209E RECORD NOT FOUND. KEY= key

Explanation: A record with the indicated key was not found in the Media Database (MDB).

Corrective Action: Contact your INCONTROL administrator for assistance.

CTT210W MEDIA mediaTypeDef OF VOLSER volser NOT FOUND IN CTTPARM

Explanation: The CTTCDB utility cannot locate the media type definition for the volume specified in the CTTPARM member. The CTTCDB utility uses media definitions in the CTTPARM member to convert volume capacity information from feet to megabytes. Since the media assigned to volume volser is not defined in CTTPARM, the default capacity is used.

The variables in this message are:

mediaTypeDef -- the missing media type definition
volser -- the volume for which the CTTCDB utility tried to find the media type definition

The utility continues processing. The capacity for volume volser is set to the default for the utility.

Corrective Action: Define med_typ_def in CTTPARM and rerun the utility.

CTT250I TRC IS FORMATTED WITH n1 BLOCKS, n2 RECORDS, n3 AVG RECORD LENGTH

Explanation: This information message is issued by the formatting program at the end of the Trace file format.

n1 -- Number of blocks
n2 -- Number of records
n3 -- Average record length

Corrective Action: No action is required.

CTT251E INDEX FILE IS NOT EMPTY

Explanation: The Index file contains active records.

The Index file must be empty before the issuing utility is started.

Processing of the utility stops.

Corrective Action: Do the following:

Use the IOADBF utility to format the Index file.
Rerun the utility.

CTT260E VOLUME vol NOT FOUND IN TMC FILE. DATASET dsn

Explanation: No volume record was found for the specified data set record in the database during conversion.

Conversion continues.

Corrective Action: No action is required.

CTT261I num type recd_type CONVERTED FROM REPORT rpt_num

Explanation: This information message indicates that the conversion program has finished converting a number of records of a specific type from the specified CA-TLMS report into Control-M/Tape format.

The variables in this message are:

num - The number of records converted.
type - The status of the specified records (ACTIVE or SCRATCH).
recd_type - The type of records converted (DATASETS or VOLUMES).
rpt_num - The number of the CA-TLMS report that was converted.

Corrective Action: No action is required.

CTT262S UNSUPPORTED TLMS nnn REPORT FORMAT

Explanation: This message indicates that the conversion program encountered a mismatched line in CA TLMS report, where nnn indicates the report number and is either 004 or 010.

Execution is terminated.

Corrective Action: Produce a corrected CA TLMS report and rerun the utility.

CTT263E VOLSER volser HAS NO FIRST VOLUME IN REPORT 004

Explanation: Due to an error in the CA TLMS report 004, the conversion program has encountered a volser that is part of a chain of volsers, but which does not indicate a first volser.

The volser is assumed to be a single volume.

Corrective Action: Produce a corrected CA TLMS report 004 and rerun the utility.

CTT264W VOLUME volser EXPIRATION DATE IS CHANGED TO PERMANENT

Explanation: The CA1 V4.9 conversion program identified a volume with EXPDT=99366. CA1 V4.9 saves expiration dates that are within keyword range, or whose year is 2000 or more, with EXPDT=99366. The conversion to Control-M/Tape cannot identify the exact expiration date.

The volume expiration date is set to permanent. The conversion program continues processing with the next record.

Corrective Action: Contact BMC Customer Support.

CTT265W UNKNOWN fieldName IN EPIC-RBA: epic_rba. VALUE: unknown_value

Explanation: The EPIC conversion program (CTTCEPC) processed the EPIC record in the specified epic_rba, and found an unknown value for the specified field name.

Possible values of fieldName are:

REC-TYPE - EPIC record type
LBL_TYPE - label type
DENSITY - density
UNT_TYPE - unit type

If the fieldName is REC-TYPE, the whole record is ignored and is not converted. In all other cases, the record containing the unknown field is converted to the Control-M/Tape Media Database using a default value for the problematic field.

Corrective Action: If the field name is known to you, consider modifying the CTTCEPC EPIC conversion program to support the field.

CTT266E UNEXPECTED DSN. RBA: epic_rba. DSN: dsn

Explanation: The EPIC conversion program (CTTCEPC) found that the specified data set name in the EPIC detail record located in the specified epic_rba is not the same as the data set name in the associated EPIC master record. This message indicates an integrity error in the EPIC database. The data set name in the EPIC master record must be identical with the data set name in the EPIC detail record.

The variables in this message are:

epic_rba -- the address of the problematic detail record in the EPIC database
dsName -- the data set name in the detail record which was inconsistent with data set name in the EPIC master record.

The conversion program terminates.

Corrective Action: Verify the integrity of the EPIC database and restart the conversion process.

CTT267W FIELD NOT NUMERIC: fieldName RBA: epic_rba VOL: volser

Explanation: The EPIC conversion program (CTTCEPC) processed the record associated with the specified volser, which is located in the listed RBA, and found a non-numeric value where a numeric value was expected in the specified field.

The variables in this message are:

fieldName - the name of the field containing the problematic value

Possible values for rc from CTVUPGDB, and their meanings, are:

rc	Explanation
OK	OK
4	End of file. Key not found.
8	Error processing the files
12	Invalid function
16	An invalid record was read.
20	Not enough storage
24	Not enough storage in the GIR file
28	Not enough storage in the GIRI file
32	There is no DBO block.
40	Invalid LRECL or KEYLEN in the data or index file. Invalid logical record in DEFGIT
48	SETPATH was not issued.
100 through 199	DBS error codes
200 through 299	DBI error codes

Possible fields are:
- FILE_SEQ - File sequence (label number).
- BLK_SIZE - Block size (BLKSIZE).
- REC_SIZE - Logical record length (LRECL).
- BLK_CNT - Block count.
- SLOT - Slot number.
- TUSE_CNT - Tape use count.
- MCYCLE - Retention cycle limit.
- RET_DAYS - Retention number of days.
epic_rba - Address of the EPIC detail record in which bad value was detected.
volser - Volume whose associated record field contains the problematic value.

The record containing the problematic field is converted to the Media Database but a default value of zero is substituted for the problematic value.

Corrective Action: Either fix the problematic field in the EPIC database and repeat the conversion process, or fix that field in the Media Database by means of the CTTMUP utility.

CTT268W NEXT VOLUME NOT FOUND FOR VOLUME: volser, DSN: dsName

Explanation: A volume chaining error was detected in the EPIC database. The specified data set name (dsName) resides on the specified volume (volser) and continues on another volume. However, the conversion program was unable to locate the continuation volume.

The conversion program continues. However, the volume chaining error will probably be propagated to the Control-M/Tape Media Database.

Corrective Action: Either fix the volume chaining error in the EPIC database and rerun the conversion program, or fix the error directly in the Control-M/Tape Media Database using the CTTMUP utility.

CTT269E CHAIN ERROR IN EPIC DATA. VOLSER: volser CUR_RECD: epic_rba

Explanation: A volume group chaining error was found in the EPIC database. The EPIC conversion program (CTTCEPC) could not create a multivolume group chain for volume volser located at record address epic_rba in the EPIC database.

The variables in this message are:

volser -- Volume ID
epic_rba -- Address of the volume record in the EPIC database

Conversion continues. However, the group chaining error found in the EPIC database is propagated to the Control-M/Tape database.

Corrective Action: Do one of the following:

Fix the chaining error in the EPIC database, and repeat the conversion process.
Fix the chaining error directly in the Control-M/Tape database using the CTTMUP utility.

CTT270E REQUEST PATH IS { data_set|volume } BUT stmt PARAMETERS CONTAIN FIELDS FROM { volume|data_set }

Explanation: Fields that are used as parameters in the INCLUDE, EXCLUDE or FIELDS statements are not valid with the specified path. Only data set fields can be used with the PATH=DATASET statement. Only volume fields can be used with the PATH=VOLUME statement.

The report is not produced.

Corrective Action: Remove the fields used as parameters that conflict with the selected path, or change the path.

CTT271E NEW EXTRACT STATEMENT IS NOT ALLOWED WHILE THE PREVIOUS ONE IS NOT CLOSED

Explanation: A new EXTRACT statement was specified before a REPORT statement was specified for the previous EXTRACT statement. A new EXTRACT block cannot be started before closing the previous EXTRACT block with a REPORT statement.

The report is not produced.

Corrective Action: Close the previous EXTRACT statement with a REPORT statement before specifying a new EXTRACT statement.

CTT275E INCLUDE/EXCLUDE STATEMENTS MUST FOLLOW AFTER stmt STATEMENT

Explanation: At least one INCLUDE or EXCLUDE statement specified for the CTTRTM or CTTVTM utility did not immediately follow the specified statement.

In the CTTRTM and CTTVTM utility, at least one INCLUDE or EXCLUDE statement must follow the TYPERET and TYPEVLT statements, respectively.

The utility stops execution.

Corrective Action: Place an INCLUDE or EXCLUDE statement immediately after the TYPERET or TYPEVLT statement. Rerun the utility.

CTT276I VOLUME vol IN USE

Explanation: This information message indicates that retention processing or vault processing is requested for the volume, but the volume is in use.

If the message is issued during retention processing, the CTTRTM utility skips the volume. If the message is issued during vault processing, the CTTVTM utility skips the volume and, if the volume is part of a multi-volume chain, the whole chain is skipped.

Corrective Action: No action is required.

CTT277E INVALID EXPDT VALUE. RC: rc

Explanation: An invalid Expiration Date as defined by the EXPDT parameter was specified in the user JCL.

The EXPDT value is ignored and the data set is given a default retention.

Corrective Action: No action is required.

CTT278I VAULT vault IN VOLUME vol IS nn IN PATTERN

Explanation: This information message indicates that the specified vault was found to be the nnth vault in the vault pattern for the specified volume.

Corrective Action: No action is required.

CTT279W CONTROL-M/TAPE IS ACTIVE, RESULTS ARE UNPREDICTABLE

Explanation: The Control-M/Tape real-time environment remained active while the CTTCDB utility was running. The Media Database records created by CTTCDB might include integrity problems.

The CTTCDB utility continues processing.

Corrective Action: If this message is issued while you are running this utility for test purposes, ignore it.

If this is a production execution of the CTTCDB utility, bring Control-M/Tape down and rerun the utility.

See the step that describes conversion of the Control-M/Tape Media Database in the Control-M/Tape chapter of the INCONTROL for z/OS Installation Guide.

CTT280W VOLUME vol DEVICE dev IGNORED. NO CORRESPONDING MEDIA IN MEDIA TABLE

Explanation: The Media Table (the DADEVICE DD statement) did not contain an entry for the device specified in the message.

The current record is ignored.

Corrective Action: If this device should be defined in the Media Table, add an entry for it. Otherwise, consider this message as an information message.

CTT281I num VOLUME/DATASET RECORDS WERE CREATED

Explanation: This information message indicates the number of records written by the Conversion From MVS Catalog utility.

Corrective Action: No action is required.

CTT282W DUPLICATE DATASET dsn (VOL: volser, LABEL: lbl) DISCARDED

Explanation: A duplicate entry was detected for the specified data set during conversion of tape management data from an MVS catalog. While scanning the MVS catalog, the catalog conversion utility detected a more recent entry with the same volume and label number.

The data set with the latest creation date is taken. The referenced data set is dropped.

Corrective Action:

If the entry is obsolete, then ignore the message and continue.
Otherwise, resolve the conflict by updating your MVS catalog and rerun the conversion process.

CTT283W OBSOLETE DATASET dsn (VOL: volser LBL: lbl) DISCARDED.

Explanation: An obsolete entry was detected for the specified data set during conversion of tape management data from an MVS Catalog. A data set with a more recent creation date and a lower label number exists on the specified volume making the current entry obsolete.

The variables in this message are:

dsn -- The data set name of the obsolete catalog entry.
volser -- Volume serial number of the obsolete catalog entry.
lbl -- Volume label of the obsolete catalog entry.

The specified catalog entry is ignored. The conversion program continues normally.

Corrective Action: No action is required.

CTT286E SPECIFIED VOLSER volser CANNOT BE {INITIALIZED | ERASED} RSN= rsn

Explanation: The CTTTPI utility determined that the specified target volser cannot be initialized or erased.

Possible values of rsn:

ACTIVE IN MDB - The specified volser is in the Media Database and its status is not SCRATCH.
ADD=N - The specified volser is not in the Media Database. The ADD=N and MDBUPDAT=Y statements were specified in the TYPERUN statement.
OPER SKIPPED - The operator responded to a program prompt with a request to skip the initialization or erasure of this volume.
OPER CANCELED - The operator responded to a program prompt with a request to cancel the execution of the CTTTPI utility.

The specified volser is not initialized or erased. Execution terminates unless the reason is OPER SKIPPED, in which case processing continues with next volser or with the next control statement.

Corrective Action: If the reason was either OPER SKIPPED or OPER CANCELED, no action is necessary.

If the reason was ACTIVE IN MDB or ADD=N examine the status of the volume in the Media Database and the parameters specified in the TYPERUN control statement. Change the settings for these if necessary.

CTT287E TAPE INITIALIZATION FAILED. PROG= pgm

Explanation: The pgm program returned a nonzero return code while trying to write a label on a tape volume. The specified program was called by the CTTTPI utility. This message is also issued if the operator responds ‘S’ (SKIP) to the IBM IEHINITT utility.

The CTTTPI utility is terminated.

Corrective Action: Examine the report produced by the pgm program, and take appropriate action.

CTT288E MOUNTED VOLUME volser CANNOT BE USED. RSN= rsn

Explanation: The CTTTPI utility determined that it could not write a new label on the mounted volume (volser).

Possible values for rsn:

ACTIVE IN MDB - The specified volser is in the Media Database, and its status is not SCRATCH.
OPER REJECTED - The operator responded to a program prompt with a request to not use the mounted volume for the requested initialization.
INVALID VOLSER - The mounted volume is not the requested volume.

The CTTTPI utility unloads the mounted volume, and requests that another volume be mounted for the initialization of the same specified target volser.

Corrective Action: Do the following:

Remove the unloaded volume from the drive.
Either mount a new volume to continue the initialization process, or check the status of the volume in the Media Database and the parameters specified in the TYPERUN control statement, and change the settings if necessary.

CTT289A MOUNT VOLUME TO BE INITIALIZED AS volser ON unit_num

Explanation: The CTTTPI utility is requesting the mounting of a volume to be initialized on the specified device number (unit_num).

The message is scrolled off the screen and is followed by an ordinary MOUNT message (from MVS or from Control-M/Tape) for file CTTTPI.UTIL.INIT. volser on device number unit_num.

Corrective Action: Do the following:

Mount the volume to be initialized as volser on the desired tape drive.
Verify that the volume is not write-protected. It is recommended that the volume be already externally labeled with the correct serial number.

CTT290E OPEN FAILED FOR TAPE DD ddName

Explanation: The CTTTPI utility was unable to access the designated tape drive using the ddName DD statement.

The CTTTPI utility is terminated.

Corrective Action: Examine the JCL printout of the job, input JCL, job console log, and the allocated device. Correct all errors and rerun the CTTTPI utility.

CTT291A CONFIRM {ERAS | INIT} unit / volser1 OLDV= volser2 (status) D= dsn : Y/UNLOAD/SKIP/CANCEL

Explanation: The CTTTPI utility is requesting operator approval to initialize or erase the volume mounted on unit unit. If the user response is Y (Yes) the new label (volser1) is written over the old one (volser2). The status (status) of volser2 is displayed in parentheses.

If no label previously existed for the volume, volser2 appears as NO-LBL in this message.

If volser2 is a standard label volume, the first data set name of the volume is shown in the message (dsn). Otherwise, the first data found on the tape (if any) is displayed in its place.

Possible values of volser2 are:

ACTIVE!! -- volser2 is ACTIVE in the Media Database.
SCRATCH -- volser2 is SCRATCH in the Media Database.
NON-MDB -- volser2 is not found in the Media Database.
???????? -- Status of the mounted volume is unknown.

Note:

If the CTTTPI utility cannot read any data from the volume, the volume may never have been written, or the volume was written by another device.

The utility waits for the user response, after which it continues processing accordingly.

Corrective Action: Enter one of the following:

Y -- Confirm the operation.
UNLOAD -- Reject the mounted volume volser2. The CTTTPI utility proceeds to request another volume to be initialized as volser1.
SKIP -- Reject the mounted volume and the specified target volser1. The CTTTPI utility proceeds with the next volser or the next control statement.
CANCEL -- Terminate the CTTTPI utility. If the status of the volser is ACTIVE!!, use this option to end the operation, unless it is certain that the volser match between the mounted volume and the other active volume in the Media Database is coincidental.

Note:

No abbreviations are allowed for the UNLOAD, SKIP, or CANCEL responses.

CTT292I INITIALIZED LABEL volser1 ON OLD VOLUME volser2

Explanation: This information message indicates that the CTTTPI utility successfully completed initialization of a volume. Label volser1 was written on a volume whose previous label was volser2. When PROTECT=NOREAD is specified, volser2 appears as UNKNWN in this message.

The CTTTPI utility continues processing with the next volser or with the next control statement.

Corrective Action: No action is required.

CTT293A VOLUME volser IS NOT IN MDB. REPLY ‘Y’ - DEFINE, ‘E’ - EXTERNAL, ‘I’ - IGNORE, ‘SKIP’ OR ‘CANCEL’

Explanation: This WTOR message is issued by the CTTTPI utility before it adds a volser to the Media Database (MDB).

The utility waits for the user’s response. It then continues processing accordingly.

Corrective Action: Enter one of the following:

Y - Add the new volume to the MDB.
E - Add the new volume to the MDB and mark it as External.
I - Ignore the addition, and initialize the tape without adding the volume to the MDB.
SKIP - Reject the specified target volume (volser). The CTTTPI utility proceeds with the next volser or the next control statement. SKIP cannot be abbreviated.
CANCEL - Terminate the CTTTPI utility. CANCEL cannot be abbreviated.

CTT294E SYNTAX ERROR IN CTTTPIV PARAMETER

Explanation: The CTTTPI utility encountered a syntax error in the value specified for the PARM in the JCL EXEC statement or in the first value passed to it by an invoking program.

The CTTTPI program terminates.

Corrective Action: Correct the error and rerun the CTTTPI utility.

CTT295I VOLUME volser1 ERASED. OLD VOLUME volser2

Explanation: This information message indicates that the CTTTPI utility successfully completed erasing information on a volume.

The variables in this message are:

volser1 - the identity of the volume that was erased
volser2 - the identity of the volume label that read from the tape

The CTTTPI utility continues processing the next volser or the next control statement.

Corrective Action: No action is required.

CTT296E TAPE I/O ERROR. ECB: ecb_add

Explanation: A tape I/O operation that was issued by the CTTTPI utility failed.

In this message, ecb_add is the Event Control Block of the unsuccessful I/O operation.

If the CTTTPI utility was erasing a tape (TAPERAS) or initializing a tape (INITT), it stops processing.

If the CTTTPI utility was mapping a tape (TAPEMAP), it repeatedly tries to perform the I/O until it reaches the I/O error limit specified in the NUMERR parameter of the TAPEMAP statement.

Corrective Action: If the CTTTPI utility stops, rerun the job or started task using a different tape unit.

Parent Topic

CTT messages