Messages CTJM00 through CTJMxx

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

CTJM01I CONTROL-M/JCL VERIFY monitor_type IS READY TO HANDLE REQUESTS

Explanation: Control-M/JCL Verify Monitor or Application Server successfully initialized the queue of Control-M/JCL Verify requests and the Cross Memory environment to access the queue.

Corrective Action: No action is required.

CTJM02E INITIALIZATION ERROR. REASON: 'error_type'-reason_code

Explanation: Control-M/JCL Verify Monitor or Application Server failed to initialize the queue of Control-M/JCL Verify requests and the Cross Memory environment to access the queue.

Corrective Action: Depending on the reason code, contact IOA/System administration or IOA technical support.

CTJM03E CONTROL-M/JCL VERIFY monitor_type ALREADY ACTIVE ON SYSTEM system_id

Explanation: Control-M/JCL Verify Monitor or Application Server is already running on the system. Only one Control-M/JCL Verify Monitor or Application Server may be activated on every system.

Corrective Action: No action is required.

CTJM04I CONTROL-M/JCL VERIFY monitor_type FINISHED PROCESSING REQUESTS

Explanation: Control-M/JCL Verify Monitor or Application Server finished processing Control-M/JCL Verify requests and removed the Cross Memory environment to access the queue of these requests. Usually issued before the monitor shuts down.

Corrective Action: No action is required.

CTJM05E INTERNAL ERROR IN MANAGING VERIFY REQUESTS. FUNCTION: 'function_name'-return_code

Explanation: Control-M/JCL Verify Monitor or Application Server failed in processing the queue of Control-M/JCL Verify requests.

Corrective Action: Contact IOA technical support.

CTJM06I MODIFY COMMAND RECEIVED: command

Explanation: Control-M/JCL Verify Monitor received Modify operator command.

Corrective Action: No action is required.

CTJM07E INVALID MODIFY COMMAND RECEIVED

Explanation: Control-M/JCL Verify Monitor received invalid Modify operator command.

Corrective Action: Recheck the Modify command requested and issue the correct one.

CTJM08I SHUT DOWN UPON REQUEST FROM OPERATOR

Explanation: Control-M/JCL Verify Monitor received STOP operator command.

Corrective Action: No action is required.

CTJM09I request_number CONTROL-M/JCL VERIFY MONITOR REQUESTS STILL IN PROGRESS. RE-ISSUE STOP LATER.

Explanation: Control-M/JCL Verify Monitor received STOP operator. But the monitor cannot shut down immediately because it currently handles JCL verification requests.

Corrective Action: Issue STOP command later, after the monitor finishes handling the JCL verification requests.

CTJM0AE INTERNAL ERROR IN EXECUTING CONTROL-M/JCL VERIFY REQUESTS. FUNCTION: 'function_name"-return_code

Explanation: Control-M/JCL Verify Monitor failed in processing of a Control-M/JCL Verify request.

Corrective Action: Contact IOA technical support.

CTJM0BE INTERNAL ERROR IN PROCESSING REMOTE CONTROL-M/JCL VERIFY REQUEST. FUNCTION: 'function_name"-return_code

Explanation: Control-M/JCL Verify Monitor failed to pass the remote
Control-M/JCL Verify request to the Control-M/JCL Verify Application Server.

Corrective Action: Contact IOA technical support.

CTJM0CE CONTROL-M/JCL VERIFY APPLICATION SERVER NOT ACTIVE. REMOTE VERIFYING DISABLED

Explanation: Control-M/JCL Verify Monitor is not able to process the request for remote verification because the Control-M/JCL Verify Application Server is not active.

Corrective Action: Start the Control-M/JCL Verify Application Server.

CTJM0DI Control-M/JCL Verify processing performed by Monitor monitor_jobname / monitor_jobid on System system_id

Explanation: Informational message added to the top of the verification report when the verification was handled by the Control-M/JCL Verify Monitor.

Corrective Action: No action is required.

CTJM0EE Control-M/JCL Verify Local Monitor is not active. Re-start the monitor

Explanation: Error message indicating that the Control-M/JCL Verify cannot perform verification because the local Control-M/JCL Verify monitor has not been started.

Corrective Action: Re-start the monitor.

CTJM0FE Control-M/JCL Verify Local Monitor internal error: error

Explanation: Error message indicating that the Control-M/JCL Verify cannot perform verification because the local Control-M/JCL Verify monitor has failed to respond.

Corrective Action: No action is required.

CTJM0GW REMOTE JCL VERIFICATION ENVIRONMENT IS NOT AVAILABLE

Explanation: Control-M/JCL Verify Application Server was not installed or activated on this system. Remote JCL Verification is not possible.

Corrective Action: If Remote JCL Verification is required, install and activate Control-M/JCL Verify Application Server. Check that message CTJM0HI is issued by Control-M/JCL Verify Monitor.

CTJM0HI THE NODE NAME IS node_id

Explanation: Informational message indicating the NODE name of the IOAGATE associated with this Control-M/JCL Verify monitor.

Corrective Action: No action is required. Remote verification requests can be processed even if no IOAGATE is associated with the local monitor.

CTJM0IE ERROR IN CREATING CTMSUB SUBTASK, RC=return_code

Explanation: Internal error in Control-M/JCL Verify monitor when it attempted to create a CTMSUB subtask. Control-M/JCL Verify monitor terminates.

Corrective Action: Contact IOA technical support.

CTJM0JE CTMSUB SUBTASK FAILED

Explanation: CTMSUB subtask of Control-M/JCL Verify monitor failed. Control-M/JCL Verify monitor terminates.

Corrective Action: Contact IOA technical support.

CTJM0KE ERROR IN THE IOA SECURITY ENVIRONMENT INITIALIZATION. RC=return_code

Explanation: Control-M/JCL Verify Monitor failed to initialize the security environment. Control-M/JCL Verify monitor terminates.

Corrective Action: Contact IOA technical support.

CTJM0LI SECURITY DEFINITIONS REFRESH POSTPONED DUE TO request_number CURRENTLY ACTIVE REQUESTS

Explanation: The MODIFY operator command NEWSECDEF (to refresh the security definitions) was received by Control-M/JCL Verify Monitor. However, it cannot be processed immediately because there are active verification request sessions currently in process. Security Refresh is postponed until there are no active verification sessions running.

Corrective Action: Later, check the IOA or Control-M/JCL Verify Monitor Log to verify whether the Security Refresh was performed.

CTJM0MI SECURITY DEFINITIONS REFRESHED SUCCESSFULLY

Explanation: The security definitions were successfully refreshed by the Control-M/JCL Verify Monitor as a result of the MODIFY Operator command NEWSECDEF.

Corrective Action: No action is required.

CTJM0NE SECURITY DEFINITIONS REFRESH FAILED. RC=return_code

Explanation: The Control-M/JCL Verify Monitor failed to refresh the security definitions (requested by the MODIFY operator command NEWSECDEF). Control-M/JCL Verify Monitor terminates.

Corrective Action: Contact IOA technical support.

CTJM0OE Access Environment not created for user user_name. RC=return_code

Explanation: Control-M/JCL Verify Monitor failed to create the security access environment for the verification request owner. JCL verification is not possible.

Corrective Action: Contact the system security administrator.

CTJM0PE User user_name not defined

Explanation: Control-M/JCL Verify Monitor failed to create the security access environment for the verification request owner because the owner is not defined in the security. JCL verification is not possible.

Corrective Action: Contact the system security administrator. For remote verification, specifying a default user for remote verification (RMTUSER=Control-M/JCL Verify installation parameter) can be used.

CTJM0QW User user_name not defined. Default User default_user_name used for Remote Verification

Explanation: The owner of the remote verification request is not defined in the target system (where the verification is to be performed). Control-M/JCL Verify used the default user for the remote verification (RMTUSER=Control-M/JCL Verify installation parameter) instead of the request owner.

Corrective Action: Contact the system security administrator.

CTJM0RW IOA security is disabled. Processing is performed using CTJMON's user id

Explanation: IOA security is not installed or is disabled. Processing is performed using CTJMON's user ID and not the requester's user ID. This may result in inaccurate verification results (for example, incorrect "user is not allowed to" messages) or might be used to bypass system security policies (for example, the user may view data that he is not allowed to view).

Corrective Action: Ensure that the IOA Security interface is properly installed. For more information, refer to the INCONTROL for z/OS Installation Guide.

CTJM11E Verification processing failed with reason_code ABEND|COMPLETION_code

Explanation: Control-M/JCL Verify processing failed with ABEND or COMPLETION code. No verification report available.

Corrective Action: Contact IOA technical support.

CTJM12E Remote Verification environment not available. Request rejected.

Explanation: XCF communications are not available, and Control-M/JCL Verify Monitor cannot locate its associated IOAGATE. Remote verification requests cannot be processed.

Message CTJM0HI is issued by Control-M/JCL Verify Monitor after it detects that the Control-M/JCL Verify Application Server has been activated, and the monitor successfully extracts its own NODE name, so that it can process remote verification requests.

Corrective Action: Activate IOAGATE, which controls the Control-M/JCL Verify Application Server. Check that message CTJM0HI is issued by Control-M/JCL Verify Monitor. Alternatively, activate XCF communications (if available, by specifying XCF=Y in the CTJPARM member), so that Control-M/JCL Verify can communicate with remote monitors using XCF, or use a remote IOAGATE to communicate with monitors in remote sysplexes.

CTJM13E Verification session not found in Control-M/JCL Verify Monitor

Explanation: An internal error occurred during processing of a Control-M/JCL Verify request.

Corrective Action: Contact IOA technical support.

CTJM14E No report produced by Control-M/JCL Verification

Explanation: Control-M/JCL Verification failed and did not create a report.

Corrective Action: Contact IOA technical support.

CTJM15E name Unable to connect to target Node node_id

Explanation: .

name - the name of the system that reported the error, or an IOAGATE node name.

node_id - the value of the NODE parameter specified in the verification request.

The NODE parameter was specified in the verification request, indicating that the verification will be performed on a remote sysplex. One of the following errors occurred:

1. There is no active IOAGATE associated with any CONTROL-M/JCL Verify monitor in the local sysplex. In this case, the local system name will appear in the name field.
2. There is an active IOAGATE, but it is not connected to another IOAGATE identified by the node name. In this case, name is the IOAGATE node name.

Corrective Action:

In case 1: Ensure that IOAGATE is started and connected to one of the Control-M/JCL Verify Monitors in the local SYSPLEX.

In case 2: Check the node name specified in the verification request. If it specifies a valid IOAGATE node name then start the corresponding IOAGATE and JCL Verify monitor on the remote SYSPLEX.

IOAGATE node names are specified in the ECAPARM member. In order to be able to communicate, the nodes must also be defined in the network map. The network map name is defined by the NETWMAP parameter in ECAPARM. For more information, refer to the INCONTROL for z/OS Installation Guide: Installing.

Notes:

1. If you need to perform the verification in the local SYSPLEX then you do not need to specify a node name, since XCF can be used.
2. A node name of ‘*’ is invalid.

CTJM16E Timeout occurred waiting for reply from Node node_id

Explanation: No response received from the remote Node within a timeout interval.

Corrective Action: Contact IOA technical support.

CTJM17E Session ABENDED in local Control-M/JCL Verify Application Server

Explanation: The processing of a Remote JCL verification request failed with ABEND in the local Control-M/JCL Verify Application Server.

Corrective Action: Contact IOA technical support.

CTJM18E Control-M/JCL Verify Monitor is not active on Node node_id

Explanation: Remote JCL verification cannot be performed on the Node displayed because Control-M/JCL Verify Monitor is not active on that Node.

Corrective Action: Start Control-M/JCL Verify Monitor on the required Node.

CTJM19E Communication with target Control-M/JCL Verify Monitor failed: FUNCTION: 'function_name"-return_code

Explanation: An internal error occurred while trying to perform a remote JCL verification. The error occurred in the communication between the Control-M/JCL Verify Application Server and the Control-M/JCL Verify Monitor on the target Node.

Corrective Action: Contact IOA technical support.

CTJM1AE Application Server not active. Remote verifying disabled

Explanation: Control-M/JCL Verify Monitor is not able to process the request for remote verification because the Control-M/JCL Verify Application Server is not active.

Corrective Action: Change NODE to make the local verification or start the Control-M/JCL Verify Application Server.

CTJM1BE system_id: IOA Environment ioa_env not found on SYSTEM system_parm

Explanation: A Control-M/JCL Verify monitor was not found on the system identified by the message.

system_id – The name of the system that reported the error.

ioa_env - The IOA environment name specified in the verification request.

system_parm – The name specified in the SYSTEM parameter.

Corrective Action: Ensure that a Control-M/JCL Verify monitor is running on system system_parm, and that the QNAME parameter in the IOAPARM member matches the "IOA Env" parameter. If NODE was specified, then ensure that it refers to the correct SYSPLEX.

Note:

1. "IOA env" is optional, and that you can specify ‘*” as the system name so that Control-M/JCL Verify will search the IOA environment in all the systems in the SYSPLEX.
2. The named IOA environment refers only to Control-M/JCL Verify monitors. Other monitors such as Control-M monitors might share the same QNAME.

CTJM1CE system_id: SYSTEM system_parm not found

Explanation: A Control-M/JCL Verify Monitor was not found in the system specified by the SYSTEM parameter.

system_id – The name of the system that reported the error.

system_parm – The name specified in the SYSTEM parameter.

Corrective Action:

1. Ensure that a Control-M/JCL Verify Monitor is running on the system specified by the SYSTEM parameter, and that the NODE parameter identifies the correct SYSPLEX.
2. If the system is located in the local SYSPLEX then remove the NODE parameter.
3. If the verification can be performed on any monitor in the SYSPLEX then do not specify the SYSTEM parameter, or use ‘*’.

CTJM1DE system_id: Auto routing - JES node node_name not found in sysplex

Explanation: Control-M/JCL Verify could not verify the member on the system identified by the JES node name, node number, or DESTID specified in a JES control statement.

system_id – The name of the system that reported the error.

node_name – The JES node name as specified directly by the user, or as translated from the JES node number or DESTID.

Corrective Action:

1. Ensure that a Control-M/JCL Verify Monitor is running on the system identified by the JES node.
2. If the system is not located in the local SYSPLEX, ensure that it is defined in the CTJJ2G member and points to the node name of IOAGATE on the remote SYSPLEX.

CTJM1EE system_id: SYSTEM system_parm and/or IOA Env ioa_env not found

Explanation: The verification was requested to be performed in a specific system and IOA environment. No matching JCL Verify monitor was found.

system_id – The name of the system that reported the error.

system_parm – The name specified in the SYSTEM parameter.

ioa_env – The IOA environment name specified in the request.

Corrective Action:

1. Ensure that a Control-M/JCL Verify monitor is running on the system specified by the SYSTEM parameter, and that the NODE parameter identifies the correct SYSPLEX.

2. If the system is located in the local SYSPLEX then remove the NODE parameter.

3. See messages CTJM1BE and CTJM1CE for errors in the SYSTEM and IOA Env parameters.

CTJM1FI XCF GROUP: xcf_group_name STATUS: xcf_status

Explanation: In response to the ‘F CTJMON,DXCF command’, the following information is shown:

xcf_group_name – XCF group name, as specified in the CTJPRM member.

xcf_status

• ENABLED: XCF communication is active
• DISABLED: XCF=N was specified in CTJPARM
• ERROR: XCF=Y XCF communications was disabled due to an error

Corrective Action: Check that the XCF group name and status match the intended configuration.

If status is ERROR:

1. Review the monitor’s console message log for previous XCF related error messages.
2. Issue D XCF,GRP,xcf_group_name,ALL to obtain more information.
3. If still unresolved, restart the monitor.

CTJM1GI SYSTEM IOA ENV IOAGATE JES NODE

Explanation: This information message provides header information about Control-M/JCL Verify monitors which joined the XCF group. CTJM1HE messages that follow provide details for each monitor. This message is issued once, in response to a ‘F CTJMON,DXCF’ command.

Corrective Action: No action is required.

CTJM1HI system qname ioagate jes node

Explanation: This information message provides detailed information about a single Control-M/JCL Verify Monitor. It is issued for each communication channel in response to a ‘F CTJMON,DXCF’ command.

system: The system name where the monitor is active.

qname: The IOA environment name specified in the IOAPARM member.

ioagate: The node name (as specified in the ECAPARM) of the IOAGATE that is associated with this monitor.

jes node: The node name of the JES running in the system identified in this message.

Corrective Action: If there is more than one monitor with a IOAGATE node name, it is recommended to move the monitor to another XCF group.

CTJM1II END

Explanation: This information message indicates the end of the output from the ‘F CTJMON,DXCF’ command.

Corrective Action: No action is required.

CTJM1JE system_id: Auto routing - SYSTEM/SYSAFF parm not found in sysplex

Explanation: Control-M/JCL Verify could not verify the member on the system identified by the JES node name, node number, or DESTID specified in a JES control statement.

system_id – The name of the system that reported the error.

parm – The SYSTEM or SYSAFF parameter as specified in the JCL.

Corrective Action: Ensure that a Control-M/JCL Verify monitor is running on the system identified by the SYSTEM or SYSAFF parameter, and in the same XCF group as the monitor to which the request was submitted.

CTJM1KI THE LOCAL IOAGATE IS DOWN

Explanation: Control-M/JCL Verify monitor has detected that the IOAGATE with which it was associated is no longer active. The IOAGATE was previously identified by message CTJM0HI.

Corrective Action: No action is required. The monitor might still be able to perform remote verifications using XCF communications and remote IOAGATEs.

CTJM1LE system_id:AutoRouting - SYSTEM/SYSAFF parm not found in jesplex

Explanation: Control-M/JCL Verify could not verify the member on the system identified in a JES control statement.

system_id – The name of the system that reported the error.

parm – The SYSTEM or SYSAFF parameter as specified in the JCL.

Corrective Action: Ensure that a Control-M/JCL Verify monitor is running on the system identified by the SYSTEM or SYSAFF parameter, and in the same XCF group as the monitor to which the request was submitted.

CTJM1ME system_id:AutoRouting - IOAGATE NODE node can't be reached

Explanation: Control-M/JCL Verify monitor failed to communicate with the IOAGATE node.

Corrective Action: No action is required. The monitor might still be able to perform remote verifications.

CTJM1NE system_id: AutoRouting - no eligible system found

Explanation: Control-M/JCL Verify could not find a system where the request could be processed.

system_id – The name of the system that reported the error.

Corrective Action: Review the system affinity related parameters (JOB SYSTEM, SYSAFF, SCHENV, JOBPARM S,SYSAFF, MAIN SYSTEM). For example, you specified SYSTEM=(-SYS1,SYS2) but currently the JESPLEX does not have any other active members.

If you still would like to verify the job remotely, specify AR=N (no Auto Routing) and a system name in the Edit macro or batch verification parameters.

CTJM1OE system_id: AutoRouting failed due to XCF error

Explanation: Auto Routing cannot be performed because of XCF related problems. Possible reasons are communication errors between monitors and internal processing errors.

system_id – The name of the system that reported the error.

Corrective Action: Do the following:

1. Verify that the monitor on the remote system is active – it might have come down while processing the request. Look for XCF related errors in the monitor job log.
2. Internal error in the monitor. Forward the monitor’s job log and DATRACE file to BMC support.

CTJM1PE system_id: AutoRouting - SYSAFF member_name not active in JESPLEX

Explanation: The JESPLEX member name specified in JOB SYSAFF parameter or JOBPARM S/SYSAFF is defined in the JESPLEX, but is not currently active on any system. Auto Routing cannot be performed. system_id is the name of the system that reported the error.

Corrective Action: Verify that the parameter specifies an active member in the JESPLEX. If the member is currently down and you still would like to verify the job remotely then specify AR=N and a system name in the Edit Macro screen or batch verification parameters.

CTJM1QE CPU TIME LIMIT EXCEEDED IN statement_type STT# statement_number statement_text

Explanation: The CPU time limit set by the STMAXCPU parameter was exceeded for the JCL statement. The error message provides the type of statement, the statement number, and the text of the JCL statement (truncated). The type of statement in which the error occurred can be one of the following:

• DO WHILE — a DO WHILE action in a rule, or a REXX exec within a DO WHILE loop
• DO REXX EXEC NAME member_name — a REXX exec triggered by a rule, identified by member name

Corrective Action: Review the logic to determine the reason for the high CPU usage (for example, an infinite loop).

CTJM1RE INTERNAL ERROR WHILE PROCESSING STT# statement_number statement_text

Explanation: An internal error occurred during the processing of the JCL statement. The error message provides the statement number and the text of the JCL statement (truncated).

Corrective Action: Contact BMC Support.

CTJM31I CONTROL-M/JCL VERIFY MONITOR ASSOCIATED WITH XCF GROUP: xcf_group_name

Explanation: Control-M/JCL Verify Monitor is successfully associated with other such monitors in the specified Cross-System Coupling Facility (XCF) Group in the SYSPLEX. Monitors within the XCF group can communicate without using IOAGATE.

xcf_group_name – XCF group name, as specified in the CTJPRM member.

Corrective Action: No action is required.

CTJM32W ASSOCIATING WITH XCF GROUP FAILED. RETURN CODE: return_code

Explanation: Control-M/JCL Verify Monitor failed to associate with other monitors in the specified Cross-System Coupling Facility (XCF) Group in the SYSPLEX. This monitor can still communicate with other Control-M/JCL Verify Monitors (for performing remote verification) via IOAGATE.

return_code: the XCF error and reason codes.

Corrective Action: The error and reason codes are listed in the IBM manual, MVS Programming: Sysplex Services Reference. If the problem persists, contact BMC technical support.

CTJM33E ERROR IN CROSS SYSTEMS COMMUNICATION: function_name-return_code diagnostic_data

Explanation: Control-M/JCL Verify Monitor failed to to pass a request via Cross-System Coupling Facility (XCF) communication between monitors running on the same SYSPLEX.

function_name – internal function name

return_code – return code from the function

diagnostic_data – additional diagnostic data

Corrective Action: Contact BMC technical support.

CTJM34I number_of_requests JCL Verify SESSIONS TERMINATED

Explanation: Control-M/JCL Verify Monitor terminated all the active sessions as a result of the TERM operator Modify command (F CTJMON,TERM)

number_of_requests – The number of requests that were terminated.

Corrective Action: No action is required.

CTJM35I THE MONITOR RUNS ON 'system_id' AND BELONGS TO IOA ENVIRONMENT 'ioa_env'

Explanation: This informational message follows CTJM31I and contains the System and IOA Environment identification for the Control-M/JCL monitor. These values are used by the monitors to communicate with each other using XCF.

Corrective Action: No action is required. You can use these values in the verification request to specify where the verification request will be processed.

CTJM36I The request was received by monitor monitor_id on system system_id

Explanation: This informational message contains the system and the started task name of the first monitor which received the Control-M/JCL Verify request (the originating system).

Corrective Action: No action is required.

CTJM37I The request was submitted by monitor monitor_id on system system_id

Explanation: This informational message follows CTJM36I and contains the system and the started task name of the monitor to which the Control-M/JCL Verify request was submitted, if it is not the same as the originating system. If Auto Routing is used, then the request might eventually be processed by another monitor, which will be identified by the CTJM0DI message.

Corrective Action: No action is required.

CTJM38I ROUTING PARAMETERS: NODE=node SYS=system_name IE=environment AR=value

Explanation: This message is issued when a routing parameter is set.

Corrective Action: No action is required.