Previous Topic

Next Topic

Book Contents

Book Index

Messages CTTH00 through CTTHxx

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

CTTHAC01 ACCDB FUNC: func FOR VOL: volser FAILED. RC= rc

Explanation: The high level API of Control-M/Tape (macro CTTACCDB) failed to perform function func for volume volser. The return code is rc.

The specified volume is not processed.

Corrective Action: For more information, see the CTTACCDB macro in the Control-M/Tape chapter of the INCONTROL for z/OS Administrator Guide.

CTTHAC02 LAST IOS FUNC: func, IOS RC=rc, IOS RSN=rsn

Explanation: The specified function for the MDB failed. This message follows message CTTHAC01, if the problem is in an operation that modifies the MDB.

The variables in this message are:

Corrective Action: See message CTT200S for a description of the return code (rc) and reason code (rsn).

CTTHC001E CONTROL-M/TAPE IS NOT FOUND.

Explanation: Control-M/Tape check running under IBM Health Checker did not find the major Control-M/Tape control block.

Corrective Action: Ensure that Control-M/Tape is active.

CTTHC002E CONTROL-M/TAPE CANNOT LOCATE AN EXIT ROUTINE FOR TLP EXIT tlp_exit. RC=rc RS=rs

Explanation: During initiation, Control-M/Tape installs its exit routines to TLP Exits. However, the Control-M/Tape check running under IBM Health Checker did not find its exit routine for the specified TLP Exit. Return code and reason code are provided for the CSVDYNEX request.

Corrective Action: Ensure that Control-M/Tape is active. In addition, ensure that the Control-M/Tape Exit routine is active for the specified exit. For more information, see Step 7, "MVS Tape Label Processing Exits installation," in the Control-M/Tape installation process in the INCONTROL for z/OS Installation Guide: Installing.

CTTHC003E TLP EXIT tlp_exit HAS NO CONTROL-M/TAPE EXIT ROUTINE exit_routine ATTACHED

Explanation: During initiation, Control-M/Tape installs its exit routines to TLP Exits. However, the Control-M/Tape check running under IBM Health Checker did not find the specified Control-M/Tape exit routine attached to the specified TLP Exit.

Corrective Action: Ensure that Control-M/Tape is active. In addition, ensure that the Control-M/Tape Exit routine is active for the TLP Exit. For more information, see Step 7, "MVS Tape Label Processing Exits installation," in the Control-M/Tape installation process in the INCONTROL for z/OS Installation Guide: Installing.

CTTHC004E CONTROL-M/TAPE EXIT ROUTINE exit_routine FOR tlp_exit TLP EXIT DISABLED

Explanation: During initiation, Control-M/Tape installs its exit routines to TLP Exits. However, the Control-M/Tape check running under IBM Health Checker found that the specified Control-M/Tape exit routine for the specified TLP Exit is disabled.

Corrective Action: Ensure that Control-M/Tape is active. In addition, ensure that the Control-M/Tape Exit routine is active for the TLP Exit. For more information, see Step 7, "MVS Tape Label Processing Exits installation," in the Control-M/Tape installation process in the INCONTROL for z/OS Installation Guide: Installing.

CTTHC005E CONTROL-M/TAPE DYNAMIC WTO INTERCEPT INACTIVE

Explanation: During initiation, Control-M/Tape installs its own WTO intercept for message modifying. However, the Control-M/Tape check running under IBM Health Checker found no active Control-M/Tape WTO intercept.

Corrective Action: Ensure that Control-M/Tape is active. For more information, see the description of the DYNWTO parameter in the INCONTROL for z/OS Installation Guide: Installing.

CTTHC006E CONTROL-M/TAPE SVC svc_num NOT USED

Explanation: During initiation, Control-M/Tape installs its own SVC routine with the SVC number specified by the SVCNUM parameter. However, the Control-M/Tape check running under IBM Health Checker found no active SVC with this number.

Corrective Action: Ensure that Control-M/Tape is active. For more information, see Step 6, "Control-M/Tape SVC installation," in the Control-M/Tape installation process in the INCONTROL for z/OS Installation Guide: Installing.

CTTHC007E CONTROL-M/TAPE SVC svc_num USED BY ANOTHER PRODUCT

Explanation: During initiation, Control-M/Tape installs its own SVC routine with the SVC number specified by the SVCNUM parameter. However, the Control-M/Tape check running under IBM Health Checker found that an SVC with this number is used by another product.

Corrective Action: Ensure that Control-M/Tape is active. For more information, see Step 6, "Control-M/Tape SVC installation," in the Control-M/Tape installation process in the INCONTROL for z/OS Installation Guide: Installing.

CTTHSC01 ACCDB FUNC: func FOR VOL: volser FAILED. RC= rc

Explanation: The high level API of Control-M/Tape (macro CTTACCDB) failed to perform function func for volume volser. The return code is rc.

The specified volume is not processed.

Corrective Action: For more information, see the CTTACCDB macro in the Control-M/Tape chapter of the INCONTROL for z/OS Administrator Guide.

CTTHSC02 LAST IOS FUNC: func, IOS RC=rc, IOS RSN=rsn

Explanation: The specified function for the MDB failed. This message follows message CTTHSC01, if the problem is in an operation that modifies the MDB.

The variables in this message are:

Corrective Action: See the CTT200S message for a description of the return code (rc) and reason code (rsn).

CTTHSC04 VOLUME: volser NOT FOUND IN MDB. UPDATE NOT PERFORMED

Explanation: This message is issued by exit SLSUX06 when the volume ejected from the robotic library is unknown to Control-M/Tape.

Processing continues. The MDB is not updated.

Corrective Action: No action is required.

CTTHSC07 LINK OF EXIT exitName SUCCESSFUL

Explanation: A Control-M/Tape exit successfully linked a similar exit of another tape management system that runs parallel to Control-M/Tape.

Corrective Action: No action is required.

CTTHSC08 LINK OF EXIT exitName FAILED

Explanation: A Control-M/Tape exit failed to link a similar exit of another tape management system (TMS) that runs parallel to Control-M/Tape. When Control-M/Tape runs in TEST mode parallel to another TMS, Control-M/Tape interface exits attempt to pass control to similar exits of the other TMS.

Corrective Action: Verify that the STEPLIB or LINKLIST library of the job contains the specified exit exitName. If the exit is in one of these libraries, refer to the messages guide for the exit.

Parent Topic

CTT messages