Messages CTTI00 through CTTIxx

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

CTTI00E RBA rba1, rba2: DUPLICATE {VOLUME | DATASET}

Explanation: The CTTIDB utility detected one of the following:

data records with the same volser in two volumes
data records with the same label number located on the same volume in two data sets
data records with the same label number located on the same multi-volume group in two data sets

In this message, rba1 and rba2 are the RBAs of these two records. This message is followed by two CTT999I information messages, which give the details about these duplicate data records.

Corrective Action: Delete one of the duplicate records by using the RECDEL statement of the CTTMUP utility, and then rebuild the equivalent index entries using the GRPBIX statement of the CTTMUP utility.

CTTI01E RBA rba: DUPLICATE {MDB | STK} x-INDEX FOUND

Explanation: The CTTIDB utility found a duplicate key in the index component of the Media database (MDB) or the Stacking database (STK). The record type and rba are reported in this message.

Corrective Action: Rebuild the relevant index file using the CTTBIX utility for the Media database or the CTTDBIB utility for Stacking database.

CTTI02E RBA rba: CHAIN ERROR: err_desc

Explanation: The CTTIDB utility detected an error in a multi-volume group. Information message CTT999I, which describes the record in error, is issued after this message. Many of the errors described by this message refer to the following fields in the volume record that hold information used to link a multi-volume group:

FIRSTVOL - the first volume of the multi-volume group
PREVVOL - the previous volser in the multi-volume group
NEXTVOL - the next volser in the multi-volume group
VOLSEQ - the volume sequence number

The variables in this message are:

rba - the RBA of a record of this multi-volume group
err_desc - text describing the type of group error

Corrective Action: The following table lists and explains the possible texts for the err_desc variable. Perform the corrective action as indicated.

Error Description and Explanation	Corrective Action

FIRST VOL IS NOT THE SAME IN ALL VOLS
The value in the FIRSTVOL field must be the same for each volume record of the multi-volume group. A volume record was detected with a different value in the FIRSTVOL field.	Determine whether the problem is the value of the FIRSTVOL field of this volume, or the NEXTVOL field of the previous volume in the chain. Use the VOLUPD function of the CTTMUP utility to update the volume record of the volume in error. Correct the indexes of the group using the GRPBIX function of the CTTMUP utility.
VOLUME IN BROKEN GROUP
The listed volume belongs to the multi-volume group, which is already recognized as broken.	Determine whether the volume belongs to a broken multi-volume chain. Use the VOLUPD function of the CTTMUP utility to update the volume record of the volume in error. Correct the indexes of the group using the GRPBIX function of the CTTMUP utility.
INVALID PREV/NEXT POINTER
The next or previous volume does not belong to this multi-volume group. The group is probably broken.	Determine whether the problem is the value of the NEXTVOL or PREVVOL fields. Use the VOLUPD function of the CTTMUP utility to update the volume record of the volume in error. Correct the indexes of the group using the GRPBIX function of the CTTMUP utility.
VOLUME OUT OF SEQUENCE
The volume sequence number should be greater by one than the sequence number of previous volume.	Determine whether the problem is the value of the VOLSEQ field. Use the VOLUPD function of the CTTMUP utility to update the volume record of the volume in error.
SCRATCH VOLUME IN THE ACTIVE CHAINACTIVE VOLUME IN THE SCRATCH CHAIN
In compatible MODE, all volumes from the same chain should have the same status (either ACTIVE or SCRATCH).	Determine whether all volumes from the same multi-volume group have the same status. Use the SCRATCH or EXTEND functions of the TI screen to correct this problem or the VOLSCR function of the CTTMUP utility.
INVALID NEXT POINTER IN THE LAST VOLUME
The last volume in the multi-volume chain should not have the NEXTVOL pointer.	Determine whether this volume is really the last volume in the group. Use the VOLUPD function of the CTTMUP utility to reset the VOLNEXT field for the last volume record.
INVALID PREV POINTER IN THE FIRST VOLUME
The first volume in the multi-volume group should not have the PREVVOL pointer.	Determine whether this volume is really the first volume in the group. Use the VOLUPD function of the CTTMUP utility to reset the VOLPREV field for the first volume record.
SINGLE VOLUME WITH WRONG SEQUENCE NUMBER
The sequence number of a single volume (not multi-volume) should be equal to one.	Determine whether this volume is really single volume and does not belong to any multi-volume group. Use the VOLUPD function of the CTTMUP utility to set the VOLSEQ field for this volume to 1.
INVALID VOLFIRST FOR 1ST VOLUME IN GROUP
The first volume field (VOLFIRST) of the volume record that is the first of a multi-volume group (according to the VOLSEQ field) must be equal to the value of the VOLSER field.	Determine whether this volume is the first volume of the multi-volume group, or a single volume. Use the VOLUPD function of the CTTMUP utility to set the VOLFIRST field to the VOLSER value.
DATASET OUT OF SEQUENCE
The label number of a data set is out of sequence with the other labels of its multi-volume group.	Determine whether the problem is that the dataset record is redundant. Use the RECDEL function of the CTTMUP utility to delete the redundant dataset record.

CTTI03E RBA rba: UNIDENTIFIED {MDB | STK} {DATA | INDEX} RECORD TYPE=x

Explanation: The CTTIDB utility detected a data record or index entry with an invalid type.

Corrective Action: For an invalid type of data record, use the CTTMUP utility to delete the record. For an invalid type of index entry, you need to rebuild the entire index file.

CTTI04E RBA rba: VOLUME volser OF THIS DATASET RECORD IS NOT FOUND

Explanation: The CTTIDB utility detected a volume specified in a dataset record (the DSVOLSER field) but the corresponding volume data record was not found. In this message, rba is the RBA of the dataset record whose volume was not found. Information message CTT999I, which describes the record in error, accompanies this message.

Corrective Action: See message CTT999I for the volser of the volume in error. Use the VOLADD function of the CTTMUP utility to add the missing volume record, or the RECDEL function to delete the redundant dataset record. The user also may decide to correct the volume name in the dataset record.

CTTI05E RBA rba: {VOL-CONT | L-INDEX} [NOT] {EXPECTED | FOUND} BUT [NOT] {FOUND | EXPECTED}

Explanation: The CTTIDB utility either detected an unexpected volume continuation record (T type) or L-index, or did not find one that was expected.

Volume continuation records are expected for single volumes or for the first volume of a multi-volume group that has more than three vaults in its vault pattern. Volume continuation records are not expected for single volumes with up to three vaults in their vault pattern, or for a chained volume that is not the first volume in its multi-volume group.

The L-index is expected for each dataset record and volume combination. For example, if a dataset spans on two volumes, then it will have two L-indexes, one for each volume.

In this message, rba is the RBA of volume record, volume continuation record, or dataset record according to the error detected. Information message CTT999I, which describes the record in error, accompanies this message.

Corrective Action: For an unexpected or expected L-index, use the GRPBIX function of the CTTMUP utility. If the error is not corrected, then rebuild the index file using the CTTBIX utility. For volume continuation record, determine the cause of the problem and correct it by deleting the unexpected volume continuation record, or update the number of vault entries in the VLTENTNM field in the volume record.

CTTI06E VOLUME volser IN USE FOR num DAYS

Explanation: The CTTIDB utility detected a volume record that is marked as being in use for num days. If a volume record is marked IN-USE for several days, it usually indicates a problem such as a system crash or a job abend.

Corrective Action: Check the USEDAYS parameter of the CTTIDB utility, and adjust it if necessary. Use the VOLUPD function of the CTTMUP utility to reset the IN-USE indicator from the volume record.

CTTI07E RBA rba: ACTIVE VOLUME WITH NO [ACTIVE] DATASETS

Explanation: The CTTIDB utility detected an active volume with no data set records or with no active data set records. In this message, rba is the RBA of the volume record. Information message CTT999I, which describes the volume record, follows this message.

Corrective Action: Request information on the volume by using the TI screen.

For a single volume: If its status should be SCRATCH, change it using the VOLSCR function of the CTTMUP utility. Otherwise, you can add new active dataset record using the DSNADD function of the CTTMUP utility, or activate one of the existing dataset records using DSNEXT function of CTTMUP utility.
For a volume that is part of a multi-volume group: Use the GRPBIX function of the CTTMUP utility to rebuild the indexes for the multi-volume group. If the error is not fixed, you will probably need to update the VOLSNUM field of a dataset record that is part of the multi-volume group.

CTTI08E RBA rba: DSN IS ACTIVE, BUT VOLUME volser IS SCRATCH

Explanation: The CTTIDB utility detected a SCRATCH volume with an ACTIVE data set. In this message, rba is the RBA of the data set record. A SCRATCH volume cannot contain ACTIVE data sets. Information message CTT999I, which describes the dataset record in error, accompanies this message.

Corrective Action: Determine if the data set and the volume should be SCRATCH or ACTIVE. Then depending on the results, do one of the following:

Change the volume status (VOLSTAT) to ACTIVE using the VOLUPD function of the CTTMUP utility.
Scratch the volume using the VOLSCR function of the CTTMUP utility.

CTTI09E RBA rba: VOLUME IS {NEITHER | BOTH} ACTIVE {NOR | AND} SCRATCH

Explanation: The CTTIDB utility detected a volume record that is either marked as both ACTIVE and SCRATCH, or is marked as neither ACTIVE nor SCRATCH. The volume must be either ACTIVE or SCRATCH, not both. In this message, rba is the record RBA of the volume record. Information message CTT999I, which describes the bad volume record, accompanies this message.

Corrective Action: Determine whether this volume should be ACTIVE or SCRATCH. Then, depending on the results, use the VOLUPD function of the CTTMUP utility to change the status (VOLSTAT) of the volume to either ACTIVE or SCRATCH.

CTTI10E RBA rba: LBLNUM num1 DIFFERS FROM HIGHEST DSN LABEL FOUND num2

Explanation: The CTTIDB utility detected a volume record for which the LBLNUM field is not equal to the highest active label number on volume. Information message CTT999I, which describes the volume record in error, accompanies this message.

The variables in this message are:

rba - the RBA of the volume record
num1 - the current value of LBLNUM field from the volume record
num2 - the label number of the highest active data set on the volume

Corrective Action: Use the VOLUPD function of the CTTMUP utility to update the LBLNUM field of the volume record to the correct value, which is num2, instead of num1. This error can also be corrected by means of the update function by using the TI screen.

CTTI11E RBA rba: ACTIVEDS num1 DIFFERS FROM # OF DSN RECORDS FOUND num2

Explanation: The CTTIDB utility detected a logical error in a volume record. Information message CTT999I, which describes the error volume record, accompanies this message.

The variables in this message are:

rba - the RBA of the volume record for which the error was detected
num1 - the volume record field ACTIVEDS, containing the number of active data sets on the volume
num2 - the number of active data set records that the utility detected on this volume

Corrective Action: Use the VOLUPD function of the CTTMUP utility to update the ACTIVEDS field of the volume record to the correct value, which is num2, instead of num1. This error can also be corrected by means of the update function by using the TI screen.

CTTI12E RBA rba: VOLSNUM num1 DIFFERS FROM # OF VOLUME RECORDS FOUND num2

Explanation: The CTTIDB utility detected a data set record in which the field value that holds the number of volumes that the data set resides on (VOLSNUM) is not correct. Information message CTT999I, which describes the dataset record in error, accompanies this message.

The variables in this message are:

rba - the RBA of the data set record
num1 - the current value of the VOLSNUM field from the data set record, holding the number of volumes occupied by the data set
num2 - the number of volume records counted by the utility for the data set

Corrective Action: Use the DSNUPD function of the CTTMUP utility to update the VOLSNUM field of the dataset record to the correct value, which is num2, instead of num1. Then use the GRPBIX function of the CTTMUP utility to rebuild the corresponding index entries.

CTTI13E RBA rba: MISSING VAULT PATTERN INFORMATION

Explanation: The CTTIDB utility detected a vaulted volume record with missing vaulting information. A vaulted volume means that one of the following flags is set on the volume record: VAULTED, PVLT, PENDVLT. Missing vault information means that the number of vault entries field (VLTENTNM) is zero.

Corrective Action: Use the VOLUPD function of the CTTMUP utility to update all vaulting information fields in the volume records (VLTENTNM, VAULT, VLTEXTYP, and VLTEXPDT), or run the CTTVTM utility with RECALC mode and INCLUDE statement on the problematic volume only.

CTTI14E RBA rba: SPECIFIED # OF VAULTS num1 DIFFERS FROM VAULT COUNT num2

Explanation: The CTTIDB utility detected a volume record whose specified number of vaults (num1) does not equal its actual vault count (num2). A volume record contains a field that specifies the number of vaults in the vault pattern of the volume (VLTENTNM). Information message CTT999I, which describes the erroneous volume record, accompanies this message.

Corrective Action: Use the VOLUPD function of the CTTMUP utility to update the VLTENTNM field of the volume record to the correct value, which is num2, instead of num1.

CTTI15E RBA rba: VAULT INFO NOT EQUAL TO VAULT INFO OF FIRST VOLUME

Explanation: The CTTIDB utility detected a chained volume record with vaulting information different from vaulting information in the volume record of the first volume of the multi-volume group. Vaulting information in the chained volume record must be identical to the vaulting information for the first volume. The following vaulting information fields of the volume records are compared: VLTENTNM, VAULT, VLTENTDT, VLTEXTYP, and VLTEXPDT. In this message, rba is the RBA of the volume record of the chained volume in error. Information message CTT999I, which describes the erroneous volume record, accompanies this message.

Corrective Action: Use the VOLUPD function of the CTTMUP utility to update the VLTENTNM, VAULT, VLTENTDT, VLTEXTYP and VLTEXPDT fields of the volume record to have the same value as in the first volume in this multi-volume group. You can also run the CTTVTM utility with RECALC mode and INCLUDE statement on all volumes belonging to that multi-volume group.

CTTI16E VLTVEXP IS INCONSISTENT WITH VAULTING INFORMATION (vault_seq)

Explanation: The CTTIDB utility detected a volume data record with incorrect information in the VLTVEXP field. This field identifies the vaulting pattern sequence number that holds the expiration type, which is VOL EXPIRE. In this message, vault_seq is the information that should be in the VLTVEXP field. Information message CTT999I, which describes the erroneous volume record and the current value of the VLTVEXP field, accompanies this message.

Corrective Action: Use the VOLUPD function of the CTTMUP utility to update the VLTVEXP field of the volume record to the correct value, which is vault_seq.

CTTI17E RBA rba: {MDB | STK} KEY NOT FOUND. RECTYPE: rec_typ, MISSING KEY: key_typ

Explanation: The CTTIDB utility detected a data record for which there is no index record (key). Information message CTT999I, which describes the record in error, accompanies this message.

The variables in this message are:

rba - the RBA of the data record
rec_typ - the data record type
key_typ - the type of the missing index

Corrective Action: If the missing index is a V-type index, use the VOLBIX function of the CTTMUP utility to rebuild this index (key). If the missing index is a L or D-type index, use the GRPBIX function of the CTTMUP utility to rebuild all multi-volume group indexes. For others index types, or if you did not succeed in fixing the error with the CTTMUP utility, rebuild the entire index file using the CTTBIX utility for the Media database or the CTTDBID utility for the Stacking database.

CTTI18E RBA rba: {MDB | STK} KEY BUILT FROM DATA REC IS NOT EQUAL TO REAL INDEX KEY

Explanation: The CTTIDB utility detected a mismatch between a data record and index entry. The index (key) generated from the data record does not match the index pointing to this record. These two indexes should be the same. In this message, rba is the RBA of the data record. Information message CTT999I, which describes the record in error, accompanies this message.

Corrective Action: For V, D, and L index types use the GRPBIX function of the CTTMUP utility to rebuild all multi-volume group indexes. For others index types, or if you did not succeed in fixing the error with the CTTMUP utility, rebuild the entire index file using the CTTBIX utility for the Media database or the CTTDBID utility for the Stacking database.

CTTI19E RBA rba: {MDB | STK} INDEX POINTS TO NOT EXISTING OR FREE DATA RECORD

Explanation: The CTTIDB utility detected an index record that points to a free data record or to one that does not exist. In this message, rba is the RBA of the data record. Information message CTT999I, which describes the record in error, accompanies this message.

Corrective Action: Rebuild the entire index file using the CTTBIX utility for the Media database or the CTTDBID utility for the Stacking database.

CTTI20E RBA rba: WRONG OR REDUNDANT L-INDEX

Explanation: The CTTIDB utility detected an L-type index pointing to an inappropriate data set record. In this message, rba is the RBA of the data record. Information message CTT999I, which describes the record in error, accompanies this message.

Corrective Action: Use the GRPBIX function of the CTTMUP utility to rebuild all indexes of this multi-volume group. If the error is not fixed, rebuild the entire Media database index file using the CTTBIX utility.

CTTI21E RBA rba1: INVALID RBA (rba2) POINTER IN THE {MDB | STK} HI-LEVEL INDEX

Explanation: The CTTIDB utility detected an invalid pointer from the HI-level index record to an inappropriate LOW-level index record.

The variables in this message are:

rba1 - the RBA of the HI-level index record
rba2 - the invalid RBA pointer found in the HI-level index record

Corrective Action: Rebuild the entire index file using CTTBIX utility for the Media database or the CTTDBID utility for the Stacking database.

CTTI22E RBA rba1: HI-LEVEL {MDB | STK} INDEX POINTER rba2 HAS NO TARGET

Explanation: The CTTIDB utility detected an HI-level index record, which has no target LOW-level index record.

The variables in this message are:

rba1 - the RBA of the problematic HI-level index record
rba2 - the invalid RBA pointer from the HI-level index record

Corrective Action: Rebuild the entire index file using the CTTBIX utility for the Media database or the CTTDBID utility for the Stacking database.

CTTI23E RBA rba: {MDB | STK} LOW LEVEL INDEX IS NOT A TARGET OF ANY HI-LEVEL INDEX

Explanation: The CTTIDB utility detected a LOW-level index record, which is not a target of any HI-level index record. In this message, rba is the RBA of the problematic LOW-level index record.

Corrective Action: Rebuild the entire index file using the CTTBIX utility for the Media database or the CTTDBID utility for the Stacking database.

CTTI24E RBA rba: DIFFERENT SL-NAME slName FOUND FOR SCRATCH VOLUME volser

Explanation: The CTTIDB utility detected a scratch volume record with different values in the VOLSER and SLNAME fields.

The variables in this message are:

rba - the RBA of the problematic volume record
slName - the value of the SLNAME field
volser - the value of the VOLSER field

Corrective Action: Delete the volume record from the media database using the CTTDLD utility, and then initialize the physical volume with a new unique volser using the CTTTPI utility. Make sure the new volser will be added to the Media database.

CTTI25E RBA rba: INVALID DATASET LABEL NUMBER EQUAL TO ZERO

Explanation: The CTTIDB utility detected a dataset record with the label number equal to zero. In this message, rba is the RBA of the problematic dataset record.

Corrective Action: Delete the invalid dataset record by using the RECDEL statement of CTTMUP utility.

CTTI26E RBA rba: INVALID {DATA | INDEX} RECORD STATUS z(X'xx') in {MDB | STK}

Explanation: The CTTIDB utility detected a record with invalid status. Valid status can be only A (active) or F (free).

The variables in this message are:

z - incorrect status value
rba - the RBA of the problematic record

Corrective Action: Manually update the record by entering either A or F as appropriate.

CTTI27E RBA rba: THE {MDB | STK} INDEX FILE IS CORRUPT

Explanation: The internal structure of the index file has been corrupted.

In this message, rba is the RBA of the problematic index record.

Corrective Action: Reformat the INDEX file and rebuild the index using the CTTBIX utility.

CTTI28E RBA rba1, rba2: SLOT IS OCCUPIED BY TWO VOLUMES: volser1, volser2

Explanation: The CTTIDB utility detected two different volumes, which occupy the same slot in the same vault.

In this message, rba1 and rba2 are RBAs of problematic volume records. This message is followed by message CTT999I, which contains information about the vault and the problematic slot number.

Corrective Action: Manually update one or both volume records by entering a correct slot number. Then run the CTTVTM utility in SLOTBLD mode.

CTTI29E RBA rba: VOLUME volser ASSIGNED TO NON-EXISTENT VAULT

Explanation: The CTTIDB utility detected the volumes, which are assigned to the vault, but the vault record does not exist.

In this message, rba is the RBA of the problematic volume record. This message is followed by message CTT999I, which contains information about the problematic vault record.

Corrective Action: Create the vault definition, using screen TV. Then run the CTTVTM utility in SLOTBLD mode.

CTTI30E RBA rba: VOLUME volser IS IN SLOT, BUT SLOT IS MARKED "VACANT"

Explanation: The CTTIDB utility detected the volume that occupied the slot, but the slot is marked as vacant.

In this message, rba is the RBA of the problematic volume record. This message is followed by message CTT999I, which contains information about the vault and the problematic slot number.

Corrective Action: Run the CTTVTM utility in SLOTBLD mode.

CTTI31E RBA rba: SLOT IS MARKED "OCCUPIED", BUT NO VOLUME IS ASSIGNED TO IT

Explanation: The CTTIDB utility detected the slot in the vault, which marked as "occupied", but there is no volume, assigned to it.

In this message, rba is the RBA of the problematic vault record. This message is followed by message CTT999I, which contains information about the vault and the problematic slot number.

Corrective Action: Run the CTTVTM utility in SLOTBLD mode.

CTTI32E RBA rba: RECVLNUM num IS INCONSISTENT WITH VAULTING INFORMATION

Explanation: The CTTIDB utility detected the volume, in which the value of the RECVLNUM field (number of the vaulting pattern "recalled from"), is inconsistent with the value of the VLTENTNM field (total number of vaulting patterns).

This message is followed by message CTT999I, which contains information about the problematic volume.

Corrective Action: Correct the problematic field using the CTTMUP utility.

CTTI33I {TOTAL | NUMBER OF errmsg} ERRORS FOUND: nn

Explanation: This information message shows statistical information about the number of appropriated errors detected by CTTIDB utility or total number of errors.

In this message, errmsg refers to the corresponding CTTIDB error message, such as CTTI00E or CTTI01E.

Corrective Action: No action is required.

CTTI34W NO VAULT RECORDS FOUND. ALL VAULTING ERROR MESSAGES BLOCKED.

Explanation: When attempting to cross-validate volume records and vault records, the CTTIDB utility found that no vault records exist in the MDB. No further vault-related error or warning messages are displayed.

Corrective Action: Run the CTTVTM utility in SLOTBLD mode to build vault records.

CTTI35E RBA rba: VOLUME volser CONTAINS INVALID SLOT NUMBER number

Explanation: The CTTIDB utility detected an invalid volume record. The slot number in the volume record is not in the range of the slots defined in the vault record.

The variables in this message are:

rba - the RBA of the problematic volume record
volser - the volser of the problematic volume record
number - the problematic slot number in the volume record

Corrective Action: Run the CTTMUP utility to change the problematic slot number to the correct one.

CTTI36E RBA rba: VOLUME volser CONTAINS MUTUALLY EXCLUSIVE STATUS FLAGS flags

Explanation: The CTTIDB utility detected status flags with mutually exclusive meanings. For example, the volume record status flags indicate that the volume is a SCRATCH volume and an ACTIVE volume.

The variables in this message are:

rba - the RBA of the problematic volume record
volser - the volser of the problematic volume record
flags - the volume record status flags (in hexadecimal format)

Corrective Action: Run the CTTMUP utility to change the problematic status flag to the correct one.

CTTI37E RBA rba: DATASET OUT OF SEQUENCE

Explanation: The CTTIDB utility detected an incorrect data set sequence among the data set records. For example, the utility found the following data set sequence: DS1, DS3, and DS2 (the data sets are not in the proper sequence) or DS1 and DS3 (data set DS2 is missing).

In this message, rba is the RBA of the first data set record out of sequence

Corrective Action: Run the CTTMUP utility to correct the incorrect data set sequence or to add the missing data set record.

CTTI38E RBA rba: VOLUME volser: INCORRECT DVLUSED VALUE value

Explanation: A negative value of DVLUSED was received by Control-M/Tape from the device. (The DVLUSED parameter is required for stacking processing.)

The variables in this message are:

rba - the RBA of the problematic volume record
volser - the volser of the problematic volume record
value - the DVLUSED value

The utility CTTIDB continues to run. The error is automatically fixed when the problematic tape is returned to the scratch pool.

Corrective Action: If stacking is used, you can also resolve the error by running the CTTMUP utility. If stacking is not used, consider this message as an information message.

Parent Topic

CTT messages