Messages CTJL00 through CTJLxx

This group includes messages for Control-M/JCL Verify products.

CTJL00E ID GOING DOWN DUE TO INTERNAL ERROR CODE error_code

Explanation: Control-M/JCL Verify Application Server subtask ID is shutting down because of internal error error_code.

Corrective Action: Contact BMC Customer Support.

CTJL01W ID NO CONNECTION WITH NODE=node

Explanation: Control-M/JCL Verify Application Server subtask ID received a remote Control-M/JCL Verify verification request for node, but there is no connection with node.

Corrective Action: Contact the Control-M/JCL Verify administrator.

CTJL02W ID NO RESPONSE RECEIVED WITHIN EXPECTED TIME INTERVAL

Explanation: Control-M/JCL Verify Application Server subtask ID received a remote Control-M/JCL Verify verification request for node and sent it to the remote node, however no reply has been received within the defined timeout.

Corrective Action: Contact the Control-M/JCL Verify administrator.

CTJL03W ID COMMUNICATION SLOWDOWN ENCOUNTERED

Explanation: Control-M/JCL Verify Application Server subtask ID attempted to send a Control-M/JCL Verify verification request to a remote node, but has been notified by IOAGATE that IOAGATE experiences a SLOWDOWN condition, with almost all available SIB type control blocks depleted.

Corrective Action: Contact the Control-M/JCL Verify administrator.

CTJL04E ID MBX INTERNAL ERROR ENCOUNTERED. FUNCTION: func RC=rc

Explanation: Control-M/JCL Verify Application Server subtask ID experienced an internal error when trying to communicate via IOAGATE, where

• func is the attempted function via IOAGATE
• rc is the return code with which the function failed

Corrective Action: Contact the Control-M/JCL Verify administrator.

CTJL05I ID TERMINATING

Explanation: Control-M/JCL Verify Application Server subtask ID is terminating.

Corrective Action: No action is required.

CTJL0CE CONTROL-M/JCL VERIFY MONITOR IS NOT ACTIVE ON NODE=node

Explanation: A remote Control-M/JCL Verify verification request has been sent to node, but could not be carried out because the Control-M/JCL Verify Monitor is not active on that node.

Corrective Action: Contact the Control-M/JCL Verify administrator.