Messages CTO0 through CTO0xx

This group includes messages for the Control-O product.

CTO001I {CONTROL-O | CTMCMEM} monitor TIMER SUBTASK STARTED. LEVEL sting

Explanation: This information message indicates the start of the Control-O TIMER task, which controls the product timer and cleanup processing.

Corrective Action: No action is required.

CTO002I {CONTROL-O | CTMCMEM} TIMER SUBTASK ENDED.

Explanation: This information message indicates the normal termination of the Control-O TIMER task which controls the product timer and cleanup processing.

Corrective Action: No action is required.

CTO004I SVCDUMP WAS CAPTURED SUCCESSFULLY.

Explanation: The Control-O or CMEM monitor successfully captured an SVC dump as a result of an internal process request.

The monitor continues to operate normally.

Corrective Action: Verify that the dump has been successfully written to the system dump files.

CTO005E SVCDUMP WAS FAILED. A PARTIAL DUMP WAS TAKEN BECAUSE THE DUMP DATA SET DID NOT HAVE SUFFICIENT SPACE.

Explanation: The Control-O or CMEM monitor tried to dump the monitor and ECSA. The dump request failed because the dump dataset is too small to contain all the areas that are dumped.

The monitor continues to operate normally.

Corrective Action: Increase the dump files, since they are too small for Control-O or CMEM requirements. Take into account that the ECSA is also dumped by the request.

CTO006E SVCDUMP CAPTURED FAILED RC 8 REASON= reason (HEX).

Explanation: The Control-O or CMEM monitor tried to dump the monitor and ECSA storage areas. The dump request failed. The SDUMPX system service returns a return code of 8.

The monitor continues to operate normally.

Corrective Action: Refer to SDUMPX Reason Codes for Return Code 08 in IBM’s MVS Programming Authorized Assembler Services Reference.

CTO007W RELEASING ORPHAN WSC AT address JOBNAME= jobName ASID= asid

Explanation: The Control-O or CMEM monitor found that the WSC block is marked as in use, but it is not in use.

The monitor continues to operate normally. It may issue an SVCDUMP request.

Corrective Action: If a SVCDUMP is taken, save it. If the message is issued often, send the following information to BMC Customer Support:

• The SVCDUMP file
• The monitor’s SYSOUTs

BMC Customer Support will analyze the dump to find why the WSC was not released.

CTO008W RELEASING TIMED-OUT WSC AT address JOBNAME= jobName ASID= asid

Explanation: The Control-O or CMEM monitor found that the WSC block has been marked as being in use for a very long time. Normally, the Control-O or CMEM process should hold the WSC block only for a very short time.

The monitor continues to operate normally. It may issue an SVCDUMP request.

Corrective Action: If a SVCDUMP is taken, save it. If the message is issued often, send the following information to BMC Customer Support:

• The SVCDUMP file
• The monitor’s SYSOUTs

BMC Customer Support will analyze the dump to find why the WSC was not released.

CTO009I TIMEOUT WSC AT address JOBNAME= jobName ASID= number

Explanation: The Control-O or CMEM monitor found that the WSC block has been marked as being in use for a very long time. Normally, the Control-O or CMEM process should hold the WSC block only for a very short time.

The monitor continues to operate normally. The monitor will check the WSC again in subsequent cycles and then decide what action to take.

Corrective Action: If a SVCDUMP is taken, save it. If the message is issued often, send the following information to BMC Customer Support:

• The SVCDUMP file
• The monitor’s SYSOUTs

BMC Customer Support will analyze the dump to find why the WSC was not released.

CTO00AE CTOTMO RESUMED AFTER ABENDING WHILE TRYING TO RELEASE A WSC

Explanation: Control-O subtask CTOTMO has resumed normal execution after abending while trying to release a WSC that was locked for a long time.

A SYSABEND is generated for the first occurrence of this abend.

Corrective Action: Send the dump to BMC Customer Support for investigation.

CTO046S 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.