Messages CTT0 through CTT0xx

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

CTT001S INTERNAL ERROR - REASON = rsn. NOTIFY THE IOA ADMINISTRATOR

Explanation: Processing failed due to internal error for the specified reason.

The program stops executing.

Corrective Action: Ask your INCONTROL administrator to notify BMC Customer Support.

CTT002S TASK taskName WAS CANCELED BY OPERATOR

Explanation: The specified task was canceled by an operator MVS CANCEL command.

The job or started task stops executing.

Corrective Action: No action is required.

CTT003S CONTROL-M/TAPE REAL-TIME ENVIRONMENT IS NOT ACTIVE

Explanation: The Control-M/Tape real-time environment exists but its status is not active, for example, SUSPEND or DORMANT. This message is issued by every component that requires an active environment to perform its function.

The requested Control-M/Tape function is not performed.

Corrective Action: Activate Control-M/Tape by starting the CTTINIT procedure with a PARM=RESUME statement before using this function.

CTT004S UNABLE TO LOCATE CONTROL-M/TAPE REAL-TIME ENVIRONMENT TABLE

Explanation: Control-M/Tape was not initialized in this CPU. The message is issued by every component that requires an active environment to function.

The requested Control-M/Tape function is not performed.

Corrective Action: Initialize Control-M/Tape by starting the CTTINIT procedure before using this function.

CTT005W LOAD OF USER EXIT exitName FAILED. EXIT DISABLED

Explanation: Loading of the specified user exit by Control-M/Tape failed.

This could be due to one of the following:

• The installation is not using this user exit and erased the default exit supplied with Control-M/Tape.
• IOA Load library is not in the load modules search list of the job (STEPLIB and Linklist).
• There is insufficient storage to load the exit.
• Another system-oriented reason. Check the MVS system log.
• A security violation was attempted.

No user checking is performed for the rule order.

Corrective Action: Notify your INCONTROL administrator.

CTT006E MEMBER memName NOT FOUND IN LIBRARY lib

Explanation: The requested member is not found in the requested library. This message may occur when the CTTINIT procedure tries to load the rules according to the rules order list specified by the DARULLST DD statement.

The requested rule is not loaded.

Corrective Action: Correct the member or library name in the rules order list, and restart the CTTINIT procedure.

CTT007S INSUFFICIENT STORAGE IN (EXTENDED) CSA

Explanation: There is insufficient storage available in the Extended Common Service Area (CSA) to load Control-M/Tape modules or tables.

If the problem occurs during the initialization process, initialization stops. If the problem occurs during a reload function, Control-M/Tape will continue to work with the existing module or table.

Corrective Action: Check why there is insufficient CSA. You may need to contact your systems programmer. After correcting the problem, reload the table or restart Control-M/Tape as necessary.

CTT008W dsn DATASET FREESPACE SHORTAGE - nn % UTILIZATION

Explanation: The number of free records in the file is below the specified utilization nn% threshold that was set at installation.

Normal processing continues.

Corrective Action: Depending on the specified data set either:

• Enlarge the file for the Media Database (MDB) or Stacking Database.
• Run the MDB backup utility to recycle the space for the Trace file.

CTT009S TRC DATASET FULL - MDB BACKUP REQUIRED

Explanation: The Trace file is full; therefore, no Media Database (MDB) updates are allowed.

The Trace file keeps every update to the MDB, mainly for recovery purposes. When the Trace file becomes full, updates to the MDB are not allowed, since they may cause data to be lost. However, when a backup is made to the MDB, the Trace file data is no longer critical, so new MDB updates can overwrite old records in the Trace file.

The currently executing function stops.

Corrective Action: Run the MDB backup utility, then rerun the failed job.

CTT010E MEDIA media DOES NOT EXIST IN CTTPARM

Explanation: The specified media is not defined. All media names must be defined in the CTTPARM installation member.

The function that is currently executing stops.

Corrective Action: Either specify a media already defined in the CTTPARM member, or add the media name to CTTPARM.

CTT011I TRACE LEVEL IS TURNED OFF

Explanation: This information message indicates that the debug level of Control-M/Tape was turned off as a result of the TRACELVL=0 parameter.

Normal processing continues.

Corrective Action: No action is required.

CTT012S action FAILED FOR MODULE modName

Explanation: The specified action (LOAD, BLDL, FIND) for the modName module failed. During the Dynamic Interface Process, the modName module was not found in the STEPLIB library nor in SYS1.LPALIB.

The currently executing function stops.

Corrective Action: Ensure that the module exists in the STEPLIB or SYS1.LPALIB library.

CTT013S FUNCTION CATALOG NOT SUPPORTED IN THIS MVS RELEASE

Explanation: An attempt was made to catalog the data sets of an external volume, but the MVS release does not support IEFEB4UV. Cataloging of the data set failed because Control-M/Tape performs online cataloging of a data set of an external volume by means of the look up value of the unit name. IEFEB4UV, which retrieves this information, was not available in early versions of the operating system.

The ENTER command was issued to add an external volume to the Media Database. In addition, Y was entered in the MVS CATALOG field to catalog the data sets of the external volume. The ENTER command triggers both cataloging and adding of the volume to the Media Database, but the cataloging is performed before adding the volume.

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

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

CTT014W INVALID UNIT NAME unitName FOR MEDIA media

Explanation: The specified unit name is not defined in MVS tables. The specified media is defined in the CTTPARM installation member as unit unitName.

Normal processing continues.

Corrective Action: Check the media definition in the CTTPARM member.

CTT015I TRACE JOB IS SET TO jobName

Explanation: This information message indicates that since CTTINIT was started with the TRACEJOB parameter, the trace job of Control-M/Tape was assigned the name jobName. The trace job sets the job name for which trace messages, printed by some Control-M/Tape components, are issued.

Corrective Action: No action is required.

CTT016E PRINT LABEL ROUTINE FAILED. RC: rc

Explanation: The print label routine failed. This message is issued after control returns from the print label routine. The print label routine calls User Exit 9, which formats the label.

The print label routine issues one of the following return code values:

• 4 - Invalid return code. User Exit 9 returned an rc other than 0 or 4.
• 8 - Invalid label width. User Exit 9 set a label width that does not meet the 1 through 72 byte width restriction.
• 12 - Invalid label size. User Exit 9 set a label width and depth combination that exceeds the maximum print buffer size (2048 bytes).

Processing continues. The label is not printed.

Corrective Action: No action is required.

CTT017W CONTROL-M/TAPE IS NOT ACTIVE IN THE SYSTEM

Explanation: The Control-M/Tape real-time environment was terminated by operator request and is no longer active in the system.

No Control-M/Tape processing takes place.

Corrective Action: Check why Control-M/Tape was brought down, and if appropriate, start the CTTINIT procedure.

CTT018E INVALID REPLY: reply

Explanation: Control-M/Tape received an invalid reply to a WTOR message from the operator.

The WTOR message is issued again.

Corrective Action: Check the possible responses for the issued WTOR message, and respond to this message accordingly.

CTT019E SMS SUBSYSTEM ERROR: RC=rc, REASON= rsn

Explanation: An error was encountered when Control-M/Tape tried to interface with DFSMS.

Message variables are:

• rc -- The DFSMS subsystem return code.
• rsn -- The DFSMS subsystem reason code.

The Control-M/Tape to DFSMS cannot retrieve information from DFSMS.

Corrective Action: Call your INCONTROL administrator for assistance.

CTT020E CTT/SMS INTERFACE NOT ACTIVE

Explanation: Control-M/Tape tried to access DFSMS information as requested by a rule, but the interface to DFSMS is not active.

The requested function is not performed.

Corrective Action: Either remove the DFSMS reference from the Control-M/Tape rules (delete all ON MGMTCLAS rules) and the Control-M/Tape MDB records, or activate the Control-M/Tape SMS interface by setting SMSINTR to Y in the Control-M/Tape TCT table.

CTT021E SMS MANAGEMENT CLASS NOT FOUND

Explanation: The Management Class of a data set was not defined to DFSMS, and was probably deleted after the data set was created. When a data set is created, a Management Class is assigned to it.

Control-M/Tape cannot determine the data set expiration date.

Corrective Action: Define the Management Class in DFSMS, or update the data set record in the Control-M/Tape Media Database (MDB) and assign a Management Class to it.

CTT022E RULE APPLICATION FAILED. RC= rc, REASON= int_diag, ret_rc, vault_rc

Explanation: Control-M/Tape attempted to apply a rule to a data set or volume but the specified retention or vaulting information in not consistent with the relevant records in the Media Database.

The variables in this message are:

• rc -- Rule return code. Possible values:
  • 8 -- Insufficient memory.
  • 12 -- Attempt to apply retention or vaulting information failed.
• int_diag -- Internal diagnostic flags.
• ret_rc -- Retention information application return code. Possible values:
  • 4 -- Expiration date type not supported.
  • 12 -- Internal error.
  • 16 -- Expiration date is non-numeric.
• vault_rc -- Vaulting information application return code. Possible values:
  • 4 -- Expiration date type not supported.
  • 8 -- Insufficient memory.
  • 16 -- Expiration date is non-numeric.

If the message was issued by the Dynamic Dataset Stacking facility, the data set is not stacked. Otherwise, the retention and/or the vault pattern of the data set may be different from what was intended, because default retention may have been applied.

Corrective Action: Check the JCL EXPDT values for errors according to return codes, and do one of the following:

• If the message indicates a memory problem, increase the region size for the job which issued the message.
• If an invalid expiration date type was detected, check the values specified for the EXPDT parameter in the JCL DD statement.

If the problem persists, send a complete description of the problem to BMC Customer Support. Include the complete message, the job log of the problematic job, and a TI screen printout of the problematic volume and data set records.

CTT023E COULD NOT FIND FIELD fieldName FOR REQUESTED RECORD TYPE

Explanation: The user requested the display of an unrecognized field in the view definition of Media Database information on the z/OS console. Only fields that exist in the requested record type, volume or data set, can be specified. However, the specified field does not exist. The name may be misspelled.

The requested information is not displayed.

Corrective Action: Correct the field name in the view. For more information, refer to the Control-M/Tape chapter in the INCONTROL for z/OS Administrator Guide.

CTT046S BLDL/LOAD FAILED FOR THE MODULE " modName "

Explanation: Loading of the modName module failed.

Possible causes are:

• The IOA Load library is not in the load modules search list (STEPLIB + Linklist).
• There is insufficient memory.
• There is some other system-oriented reason, which may be found in the syslog.

Execution might stop.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support.

CTT050S UNABLE TO BUILD TCT, RC= rc

Explanation: The Control-M/Tape Control Table could not be built dynamically.

In this message, rc is one of the following:

• 8 - IOAPARM or CTTPARM load failed.
• 12 - GETMAIN failed.

The IOA Functional monitor is terminated.

Corrective Action: Do one of the following, depending on the return code:

• If the return code is 8, check why the CTTPARM member or the IOAPARM member could not be loaded, and restart the Functional monitor.
• If the return code is 12, increase the region size of the IOA Functional monitor, and restart the Functional monitor.

CTT051W STARTING TO READ RECORDS FROM END OF TRACE FILE

Explanation: The IOA Functional monitor did not find the check point for the last record that it processed from the Trace file.

This is normal when there were no actions recorded in the Trace file since the last request was processed, when the Trace file is empty, or it has been reformatted.

Processing of the IOA Functional monitor continues. Some of the last actions to be recorded in the Trace file before the error may not be performed.

Input records from the Control-M/Tape Trace file will be read starting from the last record in the Trace file.

Corrective Action: No action is required.

CTT070W ROUTINE routineName FAILED. RC= rc

Explanation: This message indicates that an internal error occurred in a certain routine. The significance of this error depends on the utility and the severity of the failure indicated by the return code (rc).

The variables in this message are:

• routine -- Routine in which the error occurred.
• rc -- Type of error.

Refer to the specific utility in the Control-M/Tape User Guide to determine whether processing continues or stops.

Corrective Action: Examine the return code of the utility when it stops, and proceed accordingly. If you cannot continue, refer the problem to the INCONTROL administrator.

CTT072I UTILITY util IS RUNNING IN {SIMULATION | R-SIMULATE} MODE

Explanation: This information message indicates that the specified Control-M/Tape utility is running in either simulation mode (SIMULATION) or simulation restart mode (R-SIMULATE).

Corrective Action: No action is required.

CTT073I *

Explanation: The asterisk in this message is positioned directly below the error in the previous CTT700I message to show the location of the error.

The utility stops.

Corrective Action: Remove or fix error and try again.

CTT074E SERVICE svc FAILED. RC= rc, REASON= rsn

Explanation: The specified external service called by the executing utility has failed. The executing utility returns return code rc and reason code rsn.

Possible values for the service (svc), return code (rc) and reason (rsn) are:

The utility stops execution.

Corrective Action: Correct the problem according to the reason listed in the table above and rerun the utility. If you cannot correct the problem, contact BMC Customer Support.

CTT075E DUPLICATE USE OF {STATEMENT | KEYWORD} { stmt|keywd }

Explanation: A utility encountered duplicate use of a stmt statement or keywd keyword. The statement or keyword listed in the message can only be specified once.

The utility stops execution.

Corrective Action: Remove the extraneous statement or keyword.

CTT076E MANDATORY {STATEMENT | KEYWORD} { stmt|keywd } IS MISSING

Explanation: The stmt statement or keywd keyword is mandatory, but was not found in the input to the executing utility. The stmt statement or keywd keyword does not have a default, and must be specified to the utility.

The utility stops execution.

Corrective Action: Specify the required statement or keyword in the input to the utility.

CTT077E NO KEYWORDS FOUND

Explanation: A utility encountered a statement for which no keywords were specified. The statement listed in a previous message must have at least one keyword specified.

The utility stops execution.

Corrective Action: The statement was probably specified incorrectly. Check the syntax and make sure that the appropriate keywords are used for this statement.

CTT078E INVALID VALUE SPECIFIED FOR KEYWORD keywd

Explanation: An invalid value was specified for one of the keywords in the input to a utility.

In this message, keywd is the keyword with the problematic value

The utility stops execution.

Corrective Action: Fix the value of the specified keyword and rerun the utility.

CTT079E INVALID OR UNKNOWN {STATEMENT | KEYWORD}

Explanation: A utility encountered an invalid statement or keyword. The previous CTT700I message specifies the line in which the error occurs.

The utility stops.

Corrective Action: Check earlier messages for more information. Then, remove or fix the invalid statement or keyword, and try again.

CTT080W VOLUME (volser) EXCLUDED FROM OPERATION TO PREVENT MDB INTEGRITY ERRORS

Explanation: The CTTSPL utility encountered a request to COPY or MOVE a volume (the volser volume) that is part of a chain.

If a volume is removed from a chain, the MDB is corrupted. If the copied volume is MERGEd into another MDB, the MDB into which it is merged is also corrupted.

The volser volume is excluded from the COPY or MOVE operation. The utility continues processing.

Corrective Action: BMC recommends that you do one of the following:

• When ordering a MOVE or COPY operation, ensure that you do not specify any volume that is part of a chain.
• If you must perform a MOVE or COPY operation on a volume that is part of a chain, ensure that all the volumes in the chain are specified.

CTT084I NO REPORT STATEMENT SUPPLIED. REPORT NOT GENERATED.

Explanation: There is no REPORT statement for the utility.

The utility continues processing, but no report is displayed.

Corrective Action: No action is required.

CTT085I num RULES GENERATED

Explanation: This information message is displayed when the CTTSCA utility finishes processing. During the search for tape contentions, the CTTSCA utility generated num rules to prevent detected contentions from happening in the future. Rules created by the CTTSCA utility prevent data sets that should be processed simultaneously, from being stacked on the same volume.

For more information about the CTTSCA utility, see the INCONTROL for z/OS Utilities Guide.

Corrective Action: No action is required.

CTT086I num POSSIBLE CONTENTIONS DETECTED

Explanation: This information message is displayed when the CTTSCA utility finishes processing. During the search for tape contentions, the CTTSCA utility detected num possible contentions. Any two data sets processed simultaneously are considered in possible contention, if at least one of them was opened for OUTPUT. This message is accompanied by message CTT085I.

For more information about the CTTSCA utility, see the INCONTROL for z/OS Utilities Guide.

Corrective Action: No action is required.

CTT087I num STACKABLE DATASETS FOUND

Explanation: This information message is displayed when the CTTSTKR utility finishes processing. It indicates that num data sets were identified as stackable by the CTTSTKR utility.

For more information about the CTTSTKR utility, see the INCONTROL for z/OS Utilities Guide.

Corrective Action: No action is required.

CTT088E INVALID OR UNKNOWN {STATEMENT | KEYWORD} ON LINE lineNum, COLUMN col_num OF ABOVE STATEMENT

Explanation: A utility encountered an invalid statement or keyword. This message follows message CTT700I, and specifies the line and column in which the error occurred.

The utility stops.

Corrective Action: Remove or fix the invalid statement or keyword and try again.

CTT096E SCRATCH VOLUME, BUT LAST LABEL NUMBER IS NOT ZERO

Explanation: A non-specific (scratch) request was made, but the volume that was mounted is unsuitable for one of the following reasons:

• The volume already contains one or more active data sets.
• The volume status is incorrectly set.
• The last data set number on the scratch volume is greater than zero.

The specified volume is rejected and another volume is requested.

Corrective Action: Mount a scratch volume.

CTT098E TAKING LOCK OF ASVT BY FORCE

Explanation: An error was encountered while the Control-M/Tape real-time environment was trying to synchronize between subtasks of the same address space.

One of the subtasks of the address space is granted access to one of the Control-M/Tape control blocks without synchronizing this access with the other subtasks.

Corrective Action: Call your INCONTROL administrator for assistance.