Messages CTOC00 through CTOCxx

This group includes messages for the Control-O product.

CTOC02E INTERNAL ERROR, RC=rc. TD MESSAGE INTERCEPTION STOPPED

Explanation: The Control-O CICS Interface cannot intercept new CICS Transient Data (TD) messages due to a Control-O CICS Interface internal error.

Transient Data message interception is stopped.

Corrective Action: Contact BMC Customer Support.

CTOC04I CTO SUBSYSTEM subsys INACTIVE. TD MESSAGES NOT PROCESSED

Explanation: This information message indicates that the Control-O CICS Interface was activated but cannot process Transient Data (TD) messages because the Control-O monitor is not active. The Control-O CICS Interface can automate Transient Data messages only when the Control-O monitor is active.

Processing of Transient Data messages is discontinued. It will be resumed when Control-O becomes active.

Corrective Action: Start the Control-O monitor.

CTOC05I CTO SUBSYSTEM subsys IS NOW ACTIVE. TD MESSAGES ARE PROCESSED

Explanation: This informative message indicates that the processing of Transient Data (TD) messages resumes because the Control-O monitor has been activated. The Control-O CICS Interface can automate Transient Data messages only when the Control-O monitor is active.

Processing of Transient Data messages resumes.

Corrective Action: No action is required.

CTOC06E INTERNAL ABEND= (systemCode,userCode)

Explanation: The Control-O CICS Interface detected an internal abend, where systemCode is the system abend code, and userCode is the user abend code. This is the header message for messages CTOC07I, CTOC08I, CTOC09I, and CTOC10I which provide information about the abend.

A dump of the address space is produced on the first abend intercepted by the Control-O CICS Interface, and processing of the current Transient Data (TD) message is stopped. Subsequent Transient Data messages are processed.

Corrective Action: Check the dump and the related messages. If the problem is related to CICS customization, or to storage violations due to user transactions, correct the problem. Otherwise, contact BMC Customer Support.

CTOC07E CICS FUNCTION func RESOURCE res ERROR RESPONSE resp1 resp2.

Explanation: The Control-O CICS initialization interface module initialization of the IOA environment failed due to a CICS service error.

The Control-O CICS interface initialization fails. No rule is triggered for messages written to CICS transient data queues.

Corrective Action: Notify the CICS or INCONTROL administrator.

CTOC07I PSW AT TIME OF ABEND=psw CTOCTDF EP=add1 CTOEXEC EP=add2

Explanation: This information message indicates that the Control-O CICS Interface detected an internal abend. It describes the PSW at the time of the abend, and the entry points of the related Control-O modules. This message follows message CTOC06E and precedes messages CTOC08I, CTOC09I, and CTOC10I.

A dump of the address space is produced on the first abend intercepted by the Control-O CICS Interface, and processing of the current Transient Data (TD) message stops. Subsequent Transient Data messages are processed.

Corrective Action: Check the dump and the related messages. If the problem is related to CICS customization, or to storage violations due to user transactions, correct the problem. Otherwise, contact BMC Customer Support.

CTOC08I REGISTERS AT TIME OF ABEND (R0 - R15):

Explanation: This information message indicates that the Control-O CICS Interface detected an internal abend. This message is a header for messages CTOC09I and CTOC10I which detail the contents of the registers at time of abend. This message is follows messages CTOC06E and CTOC07I.

A dump of the address space is produced on the first abend intercepted by the Control-O CICS Interface, and processing of the current Transient Data (TD) message stops. Subsequent Transient Data messages are processed.

Corrective Action: Check the dump and the related messages. If the problem is related to CICS customization, or to storage violations due to user transactions, correct the problem. Otherwise, contact BMC Customer Support.

CTOC09I register0 register1 ... register7

Explanation: This information message indicates that the Control-O CICS Interface detected an internal abend. The header for this message is message CTOC08I. This message details the contents of registers 0 - 7 at time of abend. It is precedes message CTOC10I, which details the contents of registers 8 - 15.)

A dump of the address space is produced on the first abend intercepted by the Control-O CICS Interface, and processing of the current Transient Data (TD) message stops. Subsequent Transient Data messages are processed.

Corrective Action: Check the dump and the related messages. If the problem is related to CICS customization, or to storage violations due to user transactions, correct the problem. Otherwise, contact BMC Customer Support.

CTOC0AE BLDL/LOAD FAILED FOR MODULE modName

Explanation: The Control-O CICS interface initialization module CTOCTDT failed to load the modName module.

The Control-O CICS interface initialization fails. No rule is triggered for messages written to CICS transient data queues.

Corrective Action: Do the following:

1. Verify that the IOA load library is concatenated to CICS STEPLIB. If it is not, do the following, in sequence:

• Add the IOA load library to the CICS STEPLIB.
• Stop and restart the CICS.

1. Restart the Control-O CICS interface.

CTOC0BE CONTROL-O IS NOT INSTALLED. IOAPARM MUST BE SET TO CTO=Y.

Explanation: The Control-O CICS interface module initialization of the IOA environment failed because Control-O is not installed, that is, CTO is not set to Y.

The Control-O CICS interface initialization fails. No rule is triggered for messages written to CICS transient data queues.

Corrective Action: Notify the INCONTROL administrator.

CTOC0CE CTOPARM WAS NOT INITIALIZED. CHECK ERROR MESSAGES ON THE JOBLOG/SYSLOG.

Explanation: The Control-O CICS interface module initialization of the IOA environment failed because CTOPARM is not initialized.

The Control-O CICS interface initialization fails. No rule is triggered for messages written to CICS transient data queues.

Corrective Action: Notify the INCONTROL administrator.

CTOC10I register8 register9 ... register15

Explanation: This information message indicates that the Control-O CICS Interface detected an internal abend. This message follows messages CTOC08I and CTOC09I. This message details the contents of registers 8 - 15 at time of abend.

A dump of the address space is produced on the first abend intercepted by the Control-O CICS Interface, and processing of the current Transient Data (TD) message stops. Subsequent Transient Data messages are processed.

Corrective Action: Check the dump and the related messages. If the problem is related to CICS customization, or to storage violations due to user transactions, correct the problem. Otherwise, contact BMC Customer Support.

CTOC11I CONTROL-O CICS INTERFACE INITIALIZATION COMPLETED FOR SUBSYSTEM

Explanation: This information message is issued upon successful completion of the Control-O CICS Interface initialization for the specified subsystem.

Corrective Action: No action is required.

CTOC12E ERROR IN SEND TO CICS TERMINAL. EIBRESP=errCode

Explanation: The Control-O CICS Interface could not send a message to the terminal during initialization or termination. Command EXEC CICS SEND failed with error code errCode.

Corrective Action: Check the error code. If the problem is related to CICS customization, or to storage violations due to user transactions, correct the problem. Otherwise, contact BMC Customer Support.

CTOC13E RELEASE MISMATCH. THIS VERSION OF PROGRAM CTOCTDT DOES NOT SUPPORT CICS RELEASE release

Explanation: An installation error due to a release mismatch occurred. Possible errors:

• The wrong version of the CTOCTDT module was copied to the DFHRPL CICS library.
• A CICS release earlier than Release 1.7 is installed.
• CICS was upgraded without upgrading the Control-O CICS Interface.

The Control-O CICS Interface is not initialized.

Corrective Action: Copy the version of the CTOCTDT module that corresponds to the CICS release to the DFHRPL CICS library. For details, see the instructions for installing the Control-O CICS Interface, in the Control-O chapter of the INCONTROL for z/OS Installation Guide.

CTOC14E ERROR WHILE TRYING TO DETERMINE CICS LEVEL. EIBRESP=error_code

Explanation: The Control-O CICS Interface could not determine the level of the CICS release. Command EXEC CICS INQUIRE SYSTEM RELEASE failed with error code errCode.

The Control-O CICS Interface is not initialized.

Corrective Action: Check the error code, and correct accordingly. If necessary, contact BMC Customer Support.

CTOC15E ERROR IN RECEIVE FROM TERMINAL. EIBRESP=error_code

Explanation: The Control-O CICS Interface could not receive from the terminal during initialization or termination. Command EXEC CICS RECEIVE failed with the error code errCode.

The Control-O CICS Interface is not initialized or terminated.

Corrective Action: Check the error code. If the problem is related to CICS customization, or to storage violations due to user transactions, correct the problem. Otherwise, contact BMC Customer Support.

CTOC16W INIT REQUEST INVALID. INTERFACE ALREADY INITIALIZED

Explanation: An initialization request was issued, but the Control-O CICS Interface is already initialized.

The request is not processed.

Corrective Action: No action is required.

CTOC17E "PGMIDERR" ERROR IN LOADING CTOCTDF

Explanation: Load of the CTOCTDF program failed due to a program ID error. The EXEC CICS LOAD command failed. The probable cause of the error is that the CTOCTDF program is not defined in the CICS tables.

The Control-O CICS Interface is not initialized.

Corrective Action: Make sure that the CTOCTDF program was defined and copied correctly to CICS. For details, see the instructions for installing the Control-O CICS Interface, in the Control-O chapter of the INCONTROL for z/OS Installation Guide.

CTOC18E UNAUTHORIZED TO LOAD CTOCTDF

Explanation: Load of the CTOCTDF program failed because the user is not authorized to load the program.

The Control-O CICS Interface is not initialized.

Corrective Action: Perform the necessary CICS customization, or see your CICS security administrator.

CTOC19E "PGMIDERR" ERROR IN LOADING CTOCTDP

Explanation: Load of the CTOCTDP program failed due to a program ID error. The EXEC CICS LOAD command failed. The probable cause of the error is that the CTOCTDP program is not defined in the CICS tables.

The Control-O CICS Interface is not initialized.

Corrective Action: Make sure that the CTOCTDP program was defined and copied correctly to CICS. For details, see the instructions for installing the Control-O CICS Interface, in the Control-O chapter of the INCONTROL for z/OS Installation Guide.

CTOC20E UNAUTHORIZED TO LOAD CTOCTDP

Explanation: Load of the CTOCTDP program failed because the user is unauthorized to load the program.

The Control-O CICS Interface is not initialized.

Corrective Action: Perform the necessary CICS customization, or see your CICS security administrator.

CTOC21I CONTROL-O CICS INTERFACE INITIALIZATION STARTED

Explanation: This informative message is issued at the start of the Control-O CICS Interface initialization.

Corrective Action: No action is required.

CTOC24E ERROR IN EXTRACT EXIT FOR CTOCTDX. EIBRCODE(BYTES 1-2)=errCode

Explanation: The EXEC CICS EXTRACT command failed with error code errCode.

The Control-O CICS Interface is not initialized.

Corrective Action: Check the error code and correct the problem accordingly; then try to initialize the interface again. If necessary, contact BMC Customer Support.

CTOC25E INTERFACE NOT INITIALIZED. SHUT REQUEST INVALID

Explanation: A SHUT request was issued, but it was invalid since the Control-O CICS Interface was not initialized.

The request is not processed.

Corrective Action: No action is required.

CTOC26I CONTROL-O CICS INTERFACE SHUTDOWN STARTED FOR SUBSYSTEM

Explanation: This information message is issued at start of the Control-O CICS Interface shutdown for the specified subsystem.

Corrective Action: No action is required.

CTOC27I CONTROL-O CICS INTERFACE SHUTDOWN COMPLETED FOR SUBSYSTEM

Explanation: This information message is issued upon completion of the Control-O CICS Interface shutdown.

Corrective Action: No action is required.

CTOC29E "PGMIDERR" ERROR IN RELEASING CTOCTDF

Explanation: The EXEC CICS RELEASE command failed due to a program ID error.

The Control-O CICS Interface is not shut down.

Corrective Action: Activate and deactivate the Control-O CICS Interface. If the problem persists, contact BMC Customer Support.

CTOC30E UNAUTHORIZED TO RELEASE CTOCTDF

Explanation: The EXEC CICS RELEASE command failed because the user is unauthorized to release the CTOCTDF program.

The Control-O CICS Interface is not shut down.

Corrective Action: Perform the necessary CICS customization so that the user authorized to release the CTOCTDF program, or contact your CICS security administrator.

CTOC31E "PGMIDERR" ERROR IN RELEASING CTOCTDP

Explanation: The EXEC CICS RELEASE command failed due to a program ID error.

The Control-O CICS Interface is not shut down.

Corrective Action: Activate and deactivate the Control-O CICS Interface. If the problem persists, contact BMC Customer Support.

CTOC32E UNAUTHORIZED TO RELEASE CTOCTDP

Explanation: The EXEC CICS RELEASE command failed because the user is unauthorized to release the CTOCTDP program.

The Control-O CICS Interface is not shut down.

Corrective Action: Perform the necessary CICS customization so that the user is authorized to release the CTOCTDF program, or contact your CICS security administrator.

CTOC33E UNRECOGNIZED REQUEST

Explanation: A request was not recognized. The probable cause is a syntax error in a Control-O CICS Interface command issued by the user.

The command is not processed.

Corrective Action: Re-issue the request correctly. For further information, see the instructions for installing the Control-O CICS Interface, in the Control-O chapter of the INCONTROL for z/OS Installation Guide.

CTOC35E ERROR IN ENABLING CTOCTDX FOR XTDOUT EXIT. EIBRCODE(BYTES 1-2)=errCode

Explanation: Command EXEC CICS ENABLE failed with error code errCode.

The Control-O CICS Interface is not initialized.

Corrective Action: Check the error code and correct the problem accordingly; then try to initialize the interface again. If necessary, contact BMC Customer Support.

CTOC36E ERROR IN DISABLING CTOCTDX FOR XTDOUT EXIT. EIBRCODE(BYTES 1-2)=errCode

Explanation: Command EXEC CICS DISABLE failed with the error code errCode.

The Control-O CICS Interface is not shut down.

Corrective Action: Check the error code and correct the problem accordingly; then try to initialize the interface again. If necessary, contact BMC Customer Support.

CTOC37I PSW AT TIME OF ABEND=psw CTOCTDX EP=add CTOEXEC EP=add2

Explanation: This information message indicates that the Control-O CICS Interface detected an internal abend. The message details the PSW at time of abend, and the entry points of the related Control-O modules.

A dump of the address space is produced on the first abend intercepted by the Control-O CICS Interface. Processing of the current Transient Data (TD) message is stopped. Subsequent Transient Data messages are processed.

Corrective Action: Check the dump and the related messages. If the problem is related to CICS customization, or to storage violations due to user transactions, correct the problem. Otherwise, contact BMC Customer Support.

CTOC38E INTERFACE NOT INITIALIZED. DBG REQUEST INVALID

Explanation: A DBG request was issued, but it was invalid since the Control-O CICS Interface was not initialized.

The request is not processed.

Corrective Action: No action is required.

CTOC39I DBG REQUEST ACCEPTED

Explanation: Informative message issued in response to DBG request.

Corrective Action: No action is required.