Messages CTT900 through CTT9xx

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

CTT900E VALID LABELS ARE SL/NL/NSL/AL

Explanation: An invalid label type was specified in the LABEL TYPE field. The LABEL TYPE field is used to specify the label type of the external volume to be added (or modified) to the Control-M/Tape Media Database (MDB).

Valid label types are:

• SL - Standard label
• NL - No label
• NSL - Nonstandard label
• AL - ANSI label

Corrective Action: Correct the entry by specifying a valid label type.

CTT901E VALID RETENTION TYPES ARE DAY/DAT/P/C/R/M

Explanation: An invalid retention type was specified in the RETENTION field. The RETENTION field specifies a period for which an external volume should be kept. Different retention types specify different ways to calculate the duration to retain an external volume before it may be used as a scratch volume.

Valid retention types are:

• DAT - Date
• DAY - Days
• P - Permanent
• C - MVS catalog
• R - according to specified rules
• M - MVS Catalog

Corrective Action: Correct the entry by specifying a valid retention type.

CTT902E INVALID DATA ON RETENTION LINE

Explanation: Either data were specified for a retention type that does not allow additional data, or a retention type was changed to a retention type for which additional data are not allowed. The RETENTION field is used to specify a period for which an external volume should be kept. Additional data are not valid for the PERMANENT and MVS CATALOG retention types.

Corrective Action: Correct the entry by clearing out the additional data after the RETENTION field.

CTT903E VOLSER volser ALREADY EXISTS IN MDB

Explanation: An attempt was made to add a volume (volser) to the Control-M/Tape Media Database (MDB), and the volume name already exists in the MDB. The MDB contains information about all the volumes known to Control-M/Tape. The SL-NAME field must contain a unique volume identification for Control-M/Tape.

The entry is not added to the MDB, nor is the existing record in the MDB modified by any of the fields in the Check-In Volume screen.

Corrective Action: If the existing entry in the MDB refers to the external volume specified, then exit the Check-In Volume screen, or add a different external volume.

If the existing entry does not refer to the external volume specified, and they happen to share the same identification, then do the following:

1. Specify a new unique identification in the SL-NAME field. This may be a brand new ID and is used by Control-M/Tape internally. This name is not physically written on the volume.
2. Specify in the VOLSER field the value that was previously specified in the SL-NAME field (the physical volser).

The SL-NAME and VOLSER fields should contain the same value, except in cases described above in which the SL-NAME is an ID given to Control-M/Tape for internal purposes and VOLSER is the physical ID of the volume. All references to this volume using Control-M/Tape should be done using the ID in the SL-NAME field.

CTT904I VOLSER volser ADDED TO MDB

Explanation: This information message indicates that external volume volser was successfully added to the Control-M/Tape Media Database (MDB).

Corrective Action: No action is required.

CTT905E PREVIOUS DATASET FIELD MUST BE SPECIFIED

Explanation: A data set name was specified in a DATASET # field, but no value was specified in the previous DATASET # field.

DATASET # fields specify a list of data set names that appear on the external volume. The list may not contain entries separated by an empty field. This information is automatically recorded in the Media Database (MDB) whenever the external volume is read under Control-M/Tape, but only after the external volume is added to the MDB.

Corrective Action: Correct the list of data set entries by filling in the blank field or by clearing all the entries following the empty data set entry.

CTT906E AT LEAST ONE DATASET SHOULD BE SPECIFIED TO ENABLE CATALOGING

Explanation: A request was made to catalog the data sets of an external volume but no data set names were specified in the DATASET # fields. A value of Y (yes) specified in the MVS CATALOG is a request to catalog all of the volume data sets specified. If no data set names are listed, cataloging cannot be performed.

Corrective Action: Specify at least one DATASET # value or change the value of the MVS CATALOG field to N (no).

CTT907E AT LEAST ONE DATASET SHOULD BE SPECIFIED TO ENABLE CATALOG RETENTION

Explanation: The retention period of the external volume was set to MVS CATALOG, but there were no data sets specified in the DATASET # fields.

Specifying a retention type of MVS CATALOG in the RETENTION field means keep the external volume as long as the data sets on the external volume are cataloged. If no data set names are listed, no data sets are cataloged and this retention period cannot be supported.

Corrective Action: Either specify at least one DATASET # value, or change the retention type of the external volume to a type other than MVS CATALOG.

CTT908S CATALOG OF dsn FAILED. RC=rc

Explanation: A request to add an external volume to the MDB using the ENTER command and a request to catalog the data sets of the external volume by specifying Y in the MVS CATALOG field both failed. The ENTER command triggers both requests. Cataloging is performed first.

The variables in this message are:

• dsn - the name of the data set
• rc - the return code

Possible values of rc, and their explanations are shown in the following table:

The data sets are not cataloged. The external volume is not added to the MDB.

Corrective Action: Check the return code to see why the catalog attempt was unsuccessful. After the cataloging problem is resolved, try again.

CTT909E LABEL OF DATASET MUST BE HIGHER THAN lbl_num

Explanation: The label number specified in a DATASET# field is lower or equal to the previous label number. The label number of a data set must be higher than the label number of the preceding data set. The first data set in the list must have label number of 1 or higher.

Corrective Action: Correct the label number of the data set by entering a valid sequence of label numbers in the data set list.

CTT910E PREVIOUS MULTI-VOLUME SL-NAME MUST BE SPECIFIED

Explanation: An SL-NAME was specified in one of the multivolume SL-NAME fields but the previous SL-NAME field in the list was empty.

Multivolume SL-NAME fields specify a list of volumes that are spanned by the last specified data set. For example, the last data set in the list spans the SL-NAME that appears at the top of the screen as well as all the multivolume SL-NAMEs filled in at the bottom of the screen. The multivolume list may not contain two completed entries separated by a blank entry.

Corrective Action: Correct the list of multivolume SL-NAMEs either by filling in the blank entry or by clearing all the other SL-NAME fields following the blank entry.

CTT911E SL-NAME CANNOT BE SPECIFIED WITHOUT VOLSER

Explanation: An SL-NAME was specified in one of the multivolume SL-NAME fields but the corresponding VOLSER field in the list was not specified. If the SL-NAME field is specified, then the VOLSER field must also be specified. For more information, see the description of the SL-NAME concept in the section on volume processing in the Control-M/Tape User Guide.

Corrective Action: Correct the list of multivolume volsers by filling in the VOLSER field or removing the SL-NAME field.

CTT912E ADDITIONAL VOLSER volser ALREADY EXISTS IN MDB

Explanation: A volser was entered in one of the multivolume SL-NAME fields but this volser already exists in the Media Database.

Multivolume SL-NAME fields specify a list of volumes which are spanned by the last specified data set. For example, the last data set in the list spans the SL-NAME that appears at the top of the screen as well as all the multivolume SL-NAMEs filled in at the bottom of the screen. A unique value must be specified in the SL-NAME field; the volume cannot be identified with a non-unique identifier.

Corrective Action: Correct the list of multivolume SL-NAMEs by identifying the volume with a unique identifier (a new SL-NAME) which should be entered in the SL-NAME field. (In such a case, the VOLSER field should be used to hold the actual volume serial number which is not unique.)

CTT913I MULTI VOLUMES ADDED TO MDB STARTING WITH VOLSER volser

Explanation: This information message indicates that external multi volumes (volsers) were successfully added to the Control-M/Tape Media Database.

The Media Database contains information about all volumes known to Control-M/Tape. An attempt to add using command ENTER external multi volumes to the Media Database was successful. For example, the external multi volumes were entered as known volumes to the Media Database.

Corrective Action: No action is required.

CTT913S OPEN OF DDNAME "SYSPRINT" FAILED

Explanation: The opening of a print file failed.

Possible causes are:

• The DD statement SYSPRINT is missing.
• The data set described by the DD statement SYSPRINT cannot be accessed for sequential write.

The program stops executing.

Corrective Action: Correct the JCL and submit again.

CTT914E ADDITIONAL VOLSER volser HAS BEEN PREVIOUSLY SPECIFIED IN LIST

Explanation: A volser was entered in one of the multivolume SL-NAME fields but this volser already exists in one of the multivolume SL-NAME fields or in the first SL-NAME field.

Multivolume SL-NAME fields specify a list of volumes which are spanned by the last specified data set. For example, the last data set in the list spans the SL-NAME that appears at the top of the screen, as well as all the multivolume SL-NAMEs filled in at the bottom of the screen. A unique value must be specified in the SL-NAME field; the same value cannot appear twice in the same list.

Corrective Action: Correct the list of multivolume SL-NAMEs by eliminating SL-NAMEs that appear more than once in the list.

CTT915S DSN dsn ALREADY CATALOGED

Explanation: A request to add an external volume to the Media Database using the ENTER command and a request to catalog the data sets of the external volume by specifying Y in the MVS CATALOG field both failed. The ENTER command triggers both, but performs cataloging first. Cataloging of the data set failed, because one of the data sets (dsn) is already cataloged.

The data sets are not cataloged and the external volume is not added to the Media Database.

Corrective Action: Notify your system programmer. To add the external volume, change the value in the MVS CATALOG field from Y to N.

CTT916I CONTROL-M/TAPE IS NOT ACTIVE. IOA DO COMMANDS WILL HAVE NO EFFECT

Explanation: An attempt was made to process IOA DO commands with a WHEN CHECKIN statement or the RETENTION by RULES option while Control-M/Tape was not active.

IOA DO commands in matching rules are ignored. If RETENTION BY RULES is requested, no retention or vaulting pattern is set for any data set in the checked in volume.

Corrective Action: To perform IOA DO commands in matching rules, or to implement the retention and vaulting pattern defined in Control-M/Tape rules for the checked-in data sets, start Control-M/Tape by means of CTTINIT.

CTT917I RANGE OF EXTERNAL VOLUME REFERENCES BY PREFIX IS FULL

Explanation: The range of volume names using the external prefix is full. The External Volume Reference Prefix is defined in CTTPARM by the EXTRNVOL parameter. All volume names defined by this prefix are already defined in the Media Database (MDB).

The name of the volser will no longer be assigned automatically by Control-M/Tape.

Corrective Action: Fill in an alternate volser name.

CTT918I PRESS ENTER TO CONFIRM THE ADDITIONAL VOLSER LIST

Explanation: When the CTTPARM EXTRNVOL parameter is set, when entering a multi-volume data set on the TC screen (EXTERNAL VOLUME CHECK-IN SCREEN), this message requests that the user confirm each additional volume name as the volume is added.

Corrective Action: Press Enter to confirm each additional volume name.

CTT919E CONTROL-M/TAPE IS NOT ACTIVE. RETENTION BY RULES CANNOT BE REQUESTED.

Explanation: RETENTION BY RULES was specified when checking-in an external volume in screen TC while Control-M/Tape was inactive.

The retention for the checked-in volume cannot be determined. Therefore, the check-in is rejected. Control-M/Tape rules can only be applied when Control-M/Tape is active. Only manually specified retention types can be used in the TC screen when Control-M/Tape is inactive.

The online screen waits for a retention type to be manually specified for the volume.

Corrective Action: Do one of the following:

• Start Control-M/Tape using the CTTINIT procedure, and then check-in the volume.
• Manually specify a retention type for the volume in screen TC.

CTT920E INVALID UNIT NAME unitname

Explanation: The unitname unit name is not defined in the system.

The requested action fails. If issued by the CTTUGNM utility, the utility continues to process the next volume record.

Corrective Action: Perform one of the following actions:

• If issued when trying to add a tape in a TC screen, correct the unit name specified in the ON UNIT field to the correct unit name for the volume being added.
• If issued in the output of the CTTUGNM utility, the message is followed by message CTT202I, which contains the details of the failing volume. Use CTTMUP to change the unit name for this volume to be a valid unit name that is defined in the system, and rerun the CTTUGNM utility.

CTT921E UNIT NAME IS REQUIRED WHEN CATALOG=Y IS SPECIFIED

Explanation: A unit name should be specified when datasets are cataloged.

Corrective Action: Specify a valid unit name in the ON UNIT field.

CTT922E service req FAILED. UNIT=unitName RC=rc REASON=rsn

Explanation: The specified service and request for the unitname unit failed with the specified return and reason codes.

This message is followed by message CTT202I, which contains the details of the failing volume.

The CTTUGNM utility continues to process the next volume record.

Corrective Action: For the EDTINFO service, a request of RTNDEVN, a return code of 8, and a reason code of 00000001, change the unit name for this volume to be a valid unit name that is defined in the system using CTTMUP, and rerun the CTTUGNM utility.

For any other information, verify that the unit name is defined in the system and that there are devices attached to it. If not, change the unit name of the volume record to be a valid unit name and rerun the CTTUGNM utility.

CTT930I opc (type) RBA=x'rba' DT=date /time V=vol /dsn

Explanation: This information message indicates the physical recovery of a Media Database (MDB) record from the Trace file. The message is issued for every physically recovered MDB record.

The variables in this message are:

• opc - Operation code for the operation performed on the MDB.

Valid values are:

• type - Record type in the MDB.

Valid values are:

• rba - RBA of the record being updated, added, or deleted.
• date - Date portion of the record timestamp.
• time - Time portion of the record timestamp.
• vol - For DSN record, the first volume of the data set. For other record types, this field is blank.
• dsn - For DSN record, data set name. For other record types, this field is blank.

Corrective Action: No action is required.

CTT931I opc (type) U=userId /jobId DT=date /time V=vol /lbl /dsName

Explanation: This information message indicates the logical recovery of a Media Database (MDB) record from the Trace file. The message is issued for every logically recovered MDB record.

The variables in this message are:

• opc - Operation code for the operation performed on the MDB.

Valid values are:

• type - Record type in the MDB.

Valid values are:

• userId - Job name or user ID of the job that caused the record to be written.
• jobId - Jobid of the above job name or user ID.
• date - Date portion of the record timestamp.
• time - Time portion of the record timestamp.
• vol - For a data set name or cat record, the first volume of the data set. For other record types, this field is blank.
• lbl - For a data set name or cat record, label number of the data set on the volume. For other record types, this field is blank.
• dsn - For a data set name or cat record, data set name. For other record types, this field is blank.

Processing continues unless an error occurs. A later message indicates if the process is prematurely terminated. If terminated, recovery is complete up to the point of termination. All MDB records created prior to that point reflect the unrecovered situation.

Corrective Action: No action is required.

CTT932E opcode REQUIRED FOR THE FOLLOWING RECORD BUT IT WAS [NOT] FOUND IN MDB:

Explanation: The opcode action requested for the record cannot proceed. Possible causes are:

• If opcode is ADD and the record already exists in the Media Database.
• If opcode is DEL or UPD and the record does not exist in the Media Database.
• In simulation mode, this message may be issued if previous records were not added to the Media Database.

Note:

In normal mode, recovery can be successful without issuing the message.

This message precedes message CTT931I.

Processing of records continues.

Corrective Action: No action is required.

CTT934I num RECORDS WERE {DELETED | UPDATED | ADDED}

Explanation: This information message is issued at the end of a logical or physical recovery.

Corrective Action: No action is required.

CTT935E CATALOG FAILED. RC: rc DSN: dsn

Explanation: The catalog operation for the specified data set failed with the specified rc. Whenever the CTTRTM utility expires a data set, it uncatalogs the data set. When the actions of the CTTRTM run are reversed using Logical Recovery, the CTTRCV utility tries to recatalog the data set.

Corrective Action: Determine why the catalog operation failed and proceed accordingly. If the return code is 8, probably the data set is already cataloged. The meaning of other return codes is in IBM documentation for LOCATE return codes. The CTTRCV utility must run in the same catalog environment in which the CTTRTM utility ran.

CTT936E THE FOLLOWING RECORD WAS FOUND WITH DIFFERENT FIELDS IN THE TRACE FILE AND THE MDB

Explanation: A trace record to be recovered has incompatible data in the Media Database (MDB). The record was updated at least one time after its current appearance in the Trace file. The record cannot be recovered because its trace file afterimage does not match its current data in the MDB. Recovering the data will cause loss of integrity.

This message precedes message CTT931.

Recovery is not performed for all records. However, the recovery job continues running until all records to be recovered are found, and appropriate messages issued.

Corrective Action: To omit processing of the record, use INCLUDE and/or EXCLUDE statements. If you set the FORCE parameter to YES, this message is issued but recovery is performed anyway. Setting FORCE to YES may cause loss of integrity in the MDB. For more information, refer to documentation for the CTTRCV utility in the INCONTROL for z/OS Utilities Guide.

CTT937I num RECORDS ARE NOT MATCHED WITH DATA IN THE MDB

Explanation: This statistical information message issued at the end of a logical or physical recovery of the Media Database (MDB) indicates the number of records (num) that were found with different fields in the Trace file and the MDB.

Corrective Action: No action is required.

CTT950E COULD NOT ACCESS lib (mem)

Explanation: Dynamic allocation of the mem member in the specified library failed. The indicated library member should contain the rule list. It is usually found in the Control-M/Tape parameter library.

Corrective Action: Check that the DARLLIB DD statement points to a library containing the RULLIST member. If it does, check for possible I/O errors on that library.

CTT951E FILE DARSR COULD NOT BE BROWSED

Explanation: Dynamic allocation of the output file created by simulation the CTTCRSS utility failed. The probable cause of failure is that the output file could not be created by the CTTCRSS utility due to an SPF problem in the profile.

Corrective Action: Reactivate the CTTCRSS utility using CLIST CTTCRSS, and using the DEBUG parameter to get detailed information. If the failure is due to an SPF problem, correct accordingly. Otherwise, notify BMC Customer Support.

CTT952I NO RULE WAS ACTIVATED BY THESE CONDITIONS

Explanation: This information message indicates that the specified combination of conditions caused no rule to be activated.

Since no rules were activated, the simulation showed no results. However, in an identical situation, the Control-M/Tape Real Time environment would use either the JCL EXPIRATION DATE, if supplied, or the retention defaults defined in the installation parameters.

Corrective Action: No action is required.

CTT953S ONE OF THE RULES SPECIFIED BY THE RULE LIST IS INVALID

Explanation: An invalid rule definition was encountered during new RULLIST processing.

Corrective Action: Correct the invalid rule definition and rerun the CTTCRSS simulation utility. To find which rule is invalid, activate CLIST CTTCRSS using the DEBUG parameter. This parameter enables debug listings.

CTT954S INTERNAL ERROR IN "CTTCRSS"

Explanation: An unrecognized return code was issued during the processing of the CTTCRSS simulation utility.

Corrective Action: Reactivate CTTCRSS using CLIST CTTCRSS, and using the DEBUG parameter to get detailed information. Notify BMC Customer Support of the results.

CTT955S UNABLE TO LOAD NEW RULE LIST. CORRECT RULLIST FILE

Explanation: The new rules could not be loaded, probably because invalid data was found in the rule order list file specified in the RULLIST file.

The simulation terminates.

Corrective Action: Correct the RULLIST file and rerun the CTTCRSS simulation utility.

CTT961E {DATA | INDEX} RECORD DOES NOT HAVE MATCHING {INDEX | DATA} RECORD RECTYPE=type

Explanation: The CTTIDB utility detected a data or index record in the Media Database (MDB) with no corresponding index or data record. Each data record should have a corresponding index record pointing to it, and each index record should point to a data record.

This message is issued with message CTT724I, which provides additional information about the problem record (volser, rba, and optionally, label, and data set).

The utility continues processing.

Corrective Action: If this problem occurs many times, rebuild the index using the CTTBIX utility.

CTT963E INDEX RECORD DIFFERS FROM DATA

Explanation: The CTTIDB utility detected a data record whose index fields do not match the key of the index record which is pointing to the data record.

This message is issued with messages CTT202I and CTT724I. Message CTT202I indicates the differences between the data record index fields and the key fields of the index record. Message CTT724I provides additional information about the problem record (volser, rba, and optionally, label and data set).

The utility continues processing.

Corrective Action: If this problem occurs many times, rebuild the index using the CTTBIX utility.

CTT964E SPECIFIED VOLUME NUMBER (DDSVOLS#=num1) DIFFERS FROM NUMBER OF L INDEX (num2)

Explanation: The CTTIDB utility detected that the number of volumes (num1) specified in DDSVOLS# does not equal the L index count (num2). These two values should be equal. DDSVOLS# is the data set data record field that contains the number of volsers on which the data set resides. Each of these volsers should have an L index record in the Index file.

This message is issued with message CTT724I, which provides additional information about the problematic record (volser, rba, and (optionally) label and data set).

The utility continues processing.

Corrective Action: If this problem occurs many times, rebuild the index using the CTTBIX utility.

CTT967E SPECIFIED LAST DATASET VOLUME RECORD (num1) DIFFERS FROM LABEL OF LAST DATASET (num2)

Explanation: The CTTIDB utility detected a volume record whose specified number of data sets (num1) is not equal to its highest data set sequence number (num2). These values should be the same.

This message is issued with message CTT724I, which provides additional information about the problematic record (volser, rba, and optionally, its label).

The utility continues processing.

Corrective Action: Correct the problem manually using the CTTMUP utility. If the problem persists, see the INCONTROL for z/OS Utilities Guide.

CTT968E SPECIFIED NUMBER OF ACTIVE DATSETS (num1) IN VOLUME RECORD DIFFERS FROM DATASET COUNT (num2)

Explanation: The CTTIDB utility detected a volume record whose specified number of active data sets (num1) is not equal to the actual number of data sets counted (num2). These values should be the same.

This message is issued with message CTT724I, which provides additional information about the problematic record (volser, rba, and optionally, its label).

The utility continues processing.

Corrective Action: Correct the problem manually using the CTTMUP utility. If the problem persists, see the INCONTROL for z/OS Utilities Guide.

CTT969E RECORD REFERS TO A WRONG VOLUME. TYPE=type

Explanation: A Control-M/Tape utility received a record other than the specific volume record that was expected. The record received either belonged to a different volume or was not a volume record.

The utility continues processing.

Corrective Action: Do the following:

1. Use the CTTIDB utility to list all errors in the Media database.
2. Use the CTTMUP utility to correct all errors found by the CTTIDB utility.

CTT972E VOLUME vol NOT FIRST BUT HAS AN ADDITIONAL VAULT RECORD

Explanation: The CTTIDB utility detected a volume data record that is not the first volume in a multivolume data set, but has an additional vault record associated with it. Only the first volume in a multivolume chain should have an additional vault record associated with it.

This message is issued with message CTT724I, which provides additional information about the problematic record (volser, rba, and optionally its label).

The utility continues processing.

Corrective Action: Contact your database administrator for assistance.

CTT973E SPECIFIED NUMBER OF DATASET VOLUMES (num1) DIFFERS FROM VOLUME COUNT (num2)

Explanation: The CTTIDB utility detected a data set data record whose specified number of volumes (num1) does not equal its actual number of associated volumes (num2). These values should be the same.

This message is issued with message CTT724I, which provides additional information about the problematic record (volser, rba, and optionally, its label).

The utility continues processing.

Corrective Action: Contact your database administrator for assistance.

CTT975E VOLUME vol IS NOT SCRATCHED AND NOT ACTIVE

Explanation: The CTTIDB utility detected a volume data record which is not scratched, deleted, or active. A volume status should be ACTIVE, SCRATCH, or DELETED.

The utility continues processing.

Corrective Action: Contact your database administrator for assistance.

CTT976E VOLUME volser IS SCRATCH BUT DATASET ON LABEL num IS ACTIVE

Explanation: A Control-M/Tape utility detected a SCRATCH volume (volser) that contains an ACTIVE data set. All the data sets on a SCRATCH volume should be SCRATCH. This situation is probably a result of a job abend or a system crash.

The utility continues processing.

Corrective Action: Determine whether the data set and the volume should be SCRATCH or ACTIVE, and change status accordingly using the CTTMUP utility.

CTT977E status1 VOLUME volser IS INCONSISTENT WITH status2 FIRST VOLUME first_vol

Explanation: A Control-M/Tape utility detected a chained volume (volser) with a status different from the status of the first volume for this multivolume chain. This situation is probably a result of a job abend or a system crash. All data sets and volumes of a multivolume chain must have the same status.

The variables in this message are:

• status1 -- Status of the detected volume in error.
• volser -- Volume serial number of the volume in error.
• status2 -- Status of the first volume in the multi volume chain.
• first_vol -- Volume serial number of the first volume in the multivolume chain.

The utility continues processing.

Corrective Action: Determine the correct status for the volumes in this multivolume chain, and update the volumes and data sets of the group accordingly, using the CTTMUP utility.

CTT980E RBA rba: INVALID RECORD TYPE: rcrd_type

Explanation: A Control-M/Tape utility detected a Media Database record with an invalid record type.

The variables in this message are:

• rba - the record RBA
• rcrd_type - the invalid type

The utility continues processing.

Corrective Action: Contact your database administrator for assistance.

CTT982E RBA rba : ACTIVEDS(num) IS HIGHER THAN LBLNUM (lbl_num) OF VOLUME

Explanation: A Control-M/Tape utility detected a logical error in a volume record. The value in the ACTIVEDS field cannot be greater than the value in the LBLNUM field.

The variables in this message are:

• rba - Volume record RBA.
• num - The number of active data sets on the volume.
• lbl_num - The highest label (file sequence number) in use on the volume.

Information message CTT999I, which describes the record in error, is issued with this message.

The utility continues processing.

Corrective Action: Do the following:

1. Determine the correct values for ACTIVEDS and LBLNUM.
2. Use the VOLUPD function of the CTTMUP utility to set correct values for ACTIVEDS and/or LBLNUM fields.

The utility continues processing.

See message CTT999I for the volser of the volume in error. If the index record (KEY) is missing, use the VOLBIX function of the CTTMUP utility to build an index for the volume. If the data record is missing, use the VOLADD function of the CTTMUP utility to add the missing volume record.

CTT997E RBA rba : I/O ERROR WHILE TRYING TO READ VOLUME: vol

Explanation: A Control-M/Tape utility encountered an I/O error while trying to read the volume record of the specified volume. In this message, rba is the RBA of the volume record of the specified volume.

This message is accompanied by message CTT200S, which provides information on the nature of the I/O error.

The utility continues processing.

Corrective Action: Contact your database administrator for assistance.

CTT998E RBA rba : DSN num IS ACTIVE, BUT VOLUME vol IS SCRATCH

Explanation: A Control-M/Tape utility detected a SCRATCH volume with an ACTIVE data set. n is the data set label. 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 record in error, accompanies this message.

The utility continues processing.

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 volume status (VOLSTAT) to ACTIVE using the VOLUPD function of the CTTMUP utility.
• Change the data set status (DSSTAT) to SCRATCH using the DSNUPD function of the CTTMUP utility.

CTT999I rcrd_desc

Explanation: This information message describes a DATA or INDEX record in error. The nature of the error is described in the previous message.

Possible values for rcrd_desc are set out in the following table:

Possible values for DATA rcrd_desc are:

• D dsn volser lbl All fields are taken from the data set record, where:
• dsn is the data set name
• volser is the volser on which the data set starts
• lbl is the data set label
• V volser SEQ: num [FIRST: first_vol] [PREV: prev_vol] [NEXT: next_vol]All fields are taken from the volume record, where:
• volser is the volser of the volume
• num is the volume sequence number in its multivolume chain
• first_vol is the volser of the first volume in the multivolume chain
• prev_vol is the previous volume in the multivolume chain
• next_vol is the next volume in the multivolume chain

Note:

Fields (FIRSTVOL, NEXTVOL, and PREVVOL) that are empty in the volume record do not appear in text of this message.

• T volser A volume continuation record, where volser is the volser of this volume continuation record.
• B boxId media num A box record, where:
• boxId is the name of the box.
• media is the media of the box.
• num is the box record count in the Media Database

Possible values for INDEX rcrd_desc are:

• K D dsn Index to a data set record, where dsn is the data set name.
• K V volser Index to a volume record, where volser is volser of the volume.
• K L volser lbl L-type index, where:
• volser is the volser of the data set
• lbl is the data set label (file sequence number)
• K T volser Index to a volume continuation record, where volser is the volser of the volume.
• K A vault Vault index, where vault is the vault name.
• K C hex_contents Index to a control record, where hex_contents are the contents of the key in hexadecimal format.
• K B boxId media num Index to a box record, where:
• boxId is the box name
• media is the media of the box
• num is the box record count in the Media Database

Corrective Action: No action is required.