Previous Topic

Next Topic

Book Contents

Book Index

Messages CTME00 through CTMExx

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.

CTME01I type BASED JOB TRACKING INITIALIZED SUCCESSFULLY

Explanation: The type variable indicates the type of job tracking method used, either ENF or JES.

Corrective Action: No action is required.

CTME02E ERROR IN ESTABLISHING LISTENER FOR JOB STATE CHANGES. REASONerror reason CODEerror code

Explanation: An internal error occurred while Control-M attempted to initialize the ENF based job tracking method. Control-M monitor continues working, using JES based job tracking. See the explanation for CTME01I for more information about ENF and JES based job tracking methods.

Corrective Action: Save the Control-M monitor system log and contact IOA or Control-M technical support for assistance.

CTME03E ERROR IN RESUME LISTENING FOR JOB STATE CHANGES. REASONerror reason CODEerror code

Explanation: An internal error occurred while Control-M attempted to resume the ENF based job tracking method after it was temporary disabled. Control-M monitor continues working, using JES based job tracking. See the explanation for CTME01I for more information about ENF and JES based job tracking methods.

Corrective Action: Save the Control-M monitor system log and contact IOA or Control-M technical support for assistance.

CTME04E LISTENING FOR JOB STATE CHANGES ENDED ABNORMALLY AND TERMINATED. LAST POINT internal name of last check point passed

Explanation: Control-M monitor detected the abnormal termination of the ENF ‘Job Status Change’ events listening exit (established by Control-M for ENF Based Job Tracking). The ENF based job tracking is disabled because of the abnormal termination, but Control-M monitor continues working, using JES based job tracking. See the explanation for CTME01I for more information about ENF and JES based job tracking methods.

Corrective Action: Save the Control-M monitor system log and contact IOA or Control-M technical support for assistance.

CTME05E INTERNAL QUEUE ERROR IN LISTENING FOR JOB STATE CHANGES. REQUEST internal queue request CODE error code

Explanation: An internal queue error occurred while processing the ENF ‘Job Status Change’ events passed to Control-M monitor from the events listening exit (established by Control-M for ENF Based Job Tracking). The ENF based job tracking is disabled because of the abnormal termination, but Control-M monitor continues working, using JES based job tracking. See the explanation for CTME01I for more information about ENF and JES based job tracking methods.

Corrective Action: Save the Control-M monitor system log and contact IOA or Control-M technical support for assistance.

CTME06W ENF BASED JOB TRACKING IS DISABLED BY INSTALLATION PARAMETER

Explanation: The ENFENA Control-M installation parameter is set to N, specifying JES based job tracking instead of ENF based job tracking. See the explanation for CTME01I for more information about ENF and JES based job tracking methods.

Corrective Action: No action is required.

CTME07W UNKNOWN LEVEL OF NON-ACTIVE SYSPLEX MEMBER system_name

Explanation: Control-M did not recognize the z/OS level of the SYSPLEX member. As a result, Control-M does not activate the ENF based jobs tracking, but uses JES based jobs tracking instead. See the explanation for CTME01I for more information about ENF and JES based job tracking methods.

Corrective Action: If the ENF based job tracking method is required, and the actual z/OS levels of the SYSPLEX members displayed in the message are not lower than z/OS 1.11, do the following: Locate the ENFENA installation parameter in the 'Monitor Parameters' section of the CTMPARM installation member and set it to F.

CTME80S STATEMENT PARSING ERROR. RC= rc. EXECUTION WILL TERMINATE

Explanation: Highlighted, unrollable message.

An internal error occurred while building the online environment.

The online environment is not started.

Corrective Action: Try to reenter the online environment after logging out and reconnecting. If this is unsuccessful, record the message and contact BMC Customer Support.

Parent Topic

CTM messages