Previous Topic

Next Topic

Book Contents

Book Index

Messages CTW0 through CTW0xx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTW001W taskName : COMMUNICATION IS NOT ACTIVE

Explanation: Communication with the Enterprise Manager gateway was disconnected. IOAGATE reported the disconnection to the Application Server of Control-M. The task-name task of the Application Server issues this message.

The Application Server waits until communication is connected again.

Corrective Action: Check IOAGATE messages to identify and fix the communication problem.

CTW002W taskName : NO RESPONSE RECEIVED WITHIN EXPECTED TIME INTERVAL

Explanation: The Enterprise Manager gateway did not respond to an IOAGATE transmission within the time allowed.

The Control-M Application Server waits for a message from the Enterprise Manager gateway.

Corrective Action: Check the Enterprise Manager gateway to find out why it is not responding.

CTW003W taskName : COMMUNICATION SLOWDOWN

Explanation: IOAGATE buffers are full. IOAGATE can not accept any new messages from the Control-M Application Server. IOAGATE informs the Application Server. The taskName task of the Application Server tries to transmit again several times and, if it does not succeed, issues this message.

The Control-M Application Server stops.

Corrective Action: Check IOAGATE messages to try to identify and fix the problem. If necessary, contact BMC Customer Support.

CTW004E taskName : MBX INTERNAL ERROR ENCOUNTERED. FUNCTION: funcName RC= rc

Explanation: An internal error occurred in the MBX API.

The Control-M Application Server terminates.

Corrective Action: Contact BMC Customer Support.

CTW046S BLDL/LOAD FAILED FOR THE MODULE "modName "

Explanation: Loading of the modName module failed.

Possible causes are:

Execution might stop.

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

Parent Topic

CTW messages