Previous Topic

Next Topic

Book Contents

Book Index

Messages CTMH00 through CTMHxx

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.

CTMH01I CONTROL-M HEALTH CHECKER TASK STARTED

Explanation: This information message indicates that the Health Checker task has begun.

Corrective Action: No action is required.

CTMH02I CONTROL-M HEALTH CHECKER TASK DISABLED IN CTMPARM

Explanation: This information message indicates that the Control-M parameter Use Health Checker (HCHEKER) is set to N.

Corrective Action: Enable the Health Checker task by setting the Control-M parameter Use Health Checker (HCHEKER) to Y.

CTMH03E HEALTH CHECKER IS NOT SUPPORTED IN CURRENT ZOS VERSION

Explanation: This error message indicates that the operating system does not support the IBM Health Checker component.

Corrective Action: No action is required.

CTMH04E CONTROL-M SUBTASK subtask HANGING

Explanation: This error message indicates that one or more Control-M subtasks has been processing the job (displayed as part of the preceding CTMH05I message) for an unreasonably long period of time. Refer to the preceding CTMH05I message lists for additional information pertaining to the job.

The Control-M Monitor continues processing as usual. The subtask continues processing the job. The delay, however, may indicate a more severe problem.

Corrective Action: Review the system log for additional messages related to the job. Then report the problem to the Control-M administrator.

If the reason for the problem is unclear, take the following actions:

  1. Take a system (SVC) dump of the Control-M monitor’s address space, using the DUMP console command. Specify the parameter SDATA=(CSA,GRSQ,SUM,RGN,TRT).
  2. Prepare the Control-M monitor full output and contact BMC Customer Support.

If the reason for the problem is outside of Control-M, holding the job being processed and restarting the Control-M monitor may have only a temporary effect.

CTMH05I CONTROL-M SUBTASK STATUSES

Explanation: This information message indicates the start of the status information displayed by the Health Checker task. This message is followed by additional information on subtasks being monitored and either CTMH06I or CTMH04E.

Corrective Action: No action is required.

CTMH06I CURRENT STATUS OF CONTROL-M MONITOR IS OK

Explanation: This information message indicates that all tasks being monitored are processing normally. This message is preceded by CTMH05I.

Corrective Action: No action is required.

CTMH07I CONTROL-M AJF FILE CONDITION

Explanation: This information message indicates that what follows is the current status of the Active Jobs File (AJF). The following information on the AJF is listed:

Corrective Action: No action is required.

CTMH08A HEALTH CHECKER INTERFACE IS DEACTIVATED AS RESULT OF A FAILURE. REPLY CONTINUE OR RETRY

Explanation: This message indicates that the Health Checker task has encounter a problem and has stopped processing.

The Health Checker task stops processing and waits for a reply.

Corrective Action: Enter one of the following responses:

CTMH09E CONTROL-M ACTIVE JOBS FILE UTILIZATION THRESHOLD IS REACHED

Explanation: This information message indicates that the use of the Active Jobs File (AJF) has reached the threshold. This message is preceded by CTMH07I, which lists information on the size of the AJF. For more information, see the Explanation of message CTMH07I.

When the number of entries used in the AJF reaches the threshold percentage Control-M could stop ordering jobs. The threshold percentage is specified in the Control-M parameter AJFTHRSH.

Control-M could stop ordering jobs but all other functions (such as, job submission and post-processing) continue normally.

Corrective Action: Contract your INCONTROL administrator. It may be necessary to compress the Active Jobs file or to increase its size.

CTMH0AI CURRENT STATUS OF CONTROL-M AJF FILE IS OK

Explanation: This information message indicates that the use of the Active Jobs File (AJF) has not reached the threshold. This message is preceded by CTMH07I, which lists information on the size of the AJF. For more information, see the Explanation of message CTMH07I.

Corrective Action: No action is required.

CTMH0BI THE CONTROL-M MONITOR RUNNING WITH CURRENT SET OF PARAMETERS

Explanation: This message indicates there are no differences between the parameter settings currently in use and those in the CTMPARM member.

Corrective Action: No action is required.

CTMH0BE REMOTE FORCEJOB PROCESSED WITH ERRORS ON REMOTE CTM, ID: remote_Control-M_ID

Explanation: Indicates that a remote FORCEJOB request that was sent to the remote Control-M failed (the remote Control-M could not force that job). It is followed by a sequence of CTMVH0EI messages detailing the response from the remote Control-M.

Corrective Action: Correct the problem indicated by the messages and then re-attempt to force the job.

CTMH0CE FOUND SOME DIFFERENCES IN CURRENT PARAMETERS SET AND CTMPARM

Explanation: This message indicates that one or more Control-M parameters, in the CTMPARM member, are not equal to the parameter setting in the running Control-M Monitor. This message precedes CTMH0DI.

The running Control-M Monitor continues processing, however, the inconsistency between the Control-M parameters could cause unpredictable results.

Corrective Action: Review the output of the message CTMH0DI and check for unexpected parameter changes.

If the differences in the parameter settings are known, perhaps as a result of using the MODIFY command, you can ignore this exception. However, if the differences are not expected, you may need to restart the Control-M monitor or refresh the Control-M parameter settings using the following command:

F CTM_monitor,NEWPARM

CTMH0DI CTMPARM COMPARATION DETAIL REPORT

Explanation: This message precedes the listing of the Control-M parameters where differences were found between the current settings and those saved in the CTMPARM member. The listing includes the following columns:

Corrective Action: No action is required.

CTMH0EI GSR:ERROR Cancel in GSR. Authorization failure, user: user_ID rc: return_code

Explanation: Follows a CTMH0BE message, providing details from the remote Control-M of why the remote Control-M could not force that job.

Corrective Action: Correct the problem indicated by the messages and then re-attempt to force the job.

CTMH18I CONTROL-M MONITOR MEMORY USAGE CHECK

Explanation: This information message indicates that the Health Checker has begun checking memory usage (Control-M Monitor Virtual Storage Consumption).

Corrective Action: No action is required.

CTMH1BI IOALOG INDEX FILE CONDITION

Explanation: This information message indicates that the Health Checker has begun checking the condition of the IOALOG INDEX file.

Corrective Action: No action is required.

CTMH1CI CURRENT STATUS OF IOALOG INDEX IS "OK"

Explanation: This information message notifies you that the health checker has completed checking the IOALOG INDEX file, and its status is OK.

Corrective Action: No action is required.

CTMH1DE CURRENT STATUS OF IOALOG INDEX IS "NOT ACTIVE"

Explanation: Use of the IOA LOG Index file is optional, but an inactive INDEX file can slow down the process of viewing IOA log messages using ORDERID.

Corrective Action: The LOG index file can be activated dynamically using the IOALOGXC utility.

CTMH1EE CURRENT STATUS OF IOALOG INDEX IS BELOW THRESHOLD OF xx%

Explanation: The current IOALOG Index file does not fully correspond to information contained in the IOA Log file. This can slow down the process of viewing IOA log messages using ORDERID.

Corrective Action: The LOG index file can be rebuilt dynamically by using the IOALOGI utility.

CTMH1FE AVAILABLE MEMORY {ABOVE | BELOW} 16MB IS LESS THAN THRESHOLD OF xxx

Explanation: The Control-M monitor is running under a memory shortage condition. This can lead the monitor to fail.

Corrective Action: Please inform the Control-M administrator.

CTMH30E HEALTH CHECKER REQUEST FAILED: IBM HEALTH CHECKER IS NOT ACTIVE

Explanation: This error message indicates that the Health Checker task could not be processed because the IBM Health Checker component is not running.

Corrective Action: No action is required.

CTMH31W IBM HEALTH CHECKER TERMINATED

Explanation: This warning message indicates that the IBM Health Checker was stopped or ended abnormally.

Corrective Action: No action is required.

CTMH32E IBM HEALTH CHECKER REMOTE CHECK checkName FAILED; REASON=nn

Explanation: This error message indicates that one of the following remote checks, identified by checkName in the message string, failed to process correctly.

The cause of the failure can be identified by the reason code, represented by nn in the message string. The following table shows possible values for nn:

Reason

Explanation

01

OPSTART failed

02

OPCOMPLETE failed

03

ADD CHECK failed

04

Obtain PAUSE

05

Pause Request failed

06

Failed to load CTMPARM

Corrective Action: No action is required.

Parent Topic

CTM messages