Messages WKJ400 through WKJ4xx

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.

WKJ437E INVALID DATE date SPECIFIED FOR action

Explanation: While processing a CMEM or Control-O request for action FORCEJOB, ADDCOND, or DELCOND, the Control-M monitor encountered an invalid date.

The date was either not a valid date or was not in the format specified by the DATETYP parameter in the IOAPARM.

This message is followed by the WKJA59E message or the WKJC39E message which identifies the failed action.

No additional action will be taken for the failed job or table order.

Corrective Action: Make sure that the date format corresponds to the DATETYP parameter in IOAPARM.

WKJ438E INTERNAL ERROR ON THE COMMUNICATION FILE. A SNAP IS PRODUCED

Explanation: Control-M has detected mismatches in the communications file while processing SHOUT to Log records from Control-O.

Corrective Action: There are two possible causes for this problem. The corrective action depends on the cause of the problem.

Problem Cause	Corrective Action
The number of subsystem-to-monitor file (S2M) records is not the same in the CTMPARM member and in the FORMSUB2 job, the file allocation and format job.	Compare the CTMCPU statements in CTMPARM with the FORMSUB2 job that was run for each system. If the problem persists, save the snap (dump), prepare the Control-M monitor full output, and contact BMC Customer Support.
The value of the SMODE parameter in CMMPARM or CTOPARM is not F.	Ensure that the SMODE parameter in CMMPARM or CTOOPARM is set to F.

The affected records are not written to the IOA Log. A snap dump is written to the DADUMP DD statement.

WKJ439E MISSING JOB jobName IN TABLE tableName IN lib

Explanation: The jobName job was not found in the tableName table.

A FORCEJOB request for the jobName job in the tableName table failed.

This message is followed by message WKJA59E, which contains more details about the error.

No additional action will be taken for the failed job order.

Corrective Action: Check that the job exists in the indicated scheduling table. For further actions, see message WKJA59E FORCEJOB FAILED FOR JOB jobName IN TABLE tableName FROM dsn

WKJ43AI FORCEJOB jobname TABLE tablename TRIGGERED BY eventType jobname/jobid

Explanation: An informational message issued to the IOA LOG when the Control-M monitor executes a DO FORCEJOB request. The DO FORCEJOB request may be triggered by a CMEM/Control-O rule or by another Control-M job.

The message contains information about the rule or job that triggered the DO FORCEJOB request, with the following details:

jobname – Name of the forced job
tablename – Name of the forced scheduling table or the table of the forced job
eventType – Triggering event, one of the following:
- JSTART – Job started
- JEND – Job ended
- MSG – Control-O/CMEM event
jobname/jobid – Name and/or ID of the triggering job

Corrective Action: No action is required.

WKJ43EW JOB jobName (OID=orderId) HUNG IN SUBMISSION

Explanation: The jobName job is used to trigger a Control-O or CMEM ON JOBARRIV rule that contains a DO FORCEJOB command. However, the jobName job has been hung in submission status for several seconds.

Control-M does not order and submit the job identified in the DO FORCEJOB command.

Corrective Action: Consider manually forcing the job identified in the DO FORCEJOB command.

WKJ43FI TRIGGER JOB jobName (jobId) NOT FORCED

Explanation: The jobName job is used to trigger a Control-O or CMEM ON JOBARRIV rule that contains a DO FORCEJOB command. However, the jobName job is one of the following:

a cyclic job found on the Active Jobs file
hung in submission status
currently being handled by one of the local sysplex monitors

Control-M does not order and submit the job identified in the DO FORCEJOB command.

Corrective Action: Do the following:

Check to see if JES is hung. If it is, find out why, and address that problem.
Consider how to act in relation to
the jobName job, that is, the job that is hung
the job identified in the DO FORCEJOB command

WKJ440I CONTROL-M MONITOR IS READY TO RECEIVE CMEM REQUESTS

Explanation: This information message indicates that the CMEM facility in the Control-M monitor was successfully initialized and the Control-M monitor is ready to accept requests from Control-O or from CMEM subsystem functions.

Corrective Action: No action is required.

WKJ441E CONTROL-M MONITOR CMEM FACILITY IS DEACTIVATED AS A RESULT OF A FAILURE

Explanation: Highlighted, unrollable message.

A severe error has occurred while processing requests from one of the following:

Control-O
CMEM subsystem functions
Control-M DO FORCEJOB

Information about the error which caused the deactivation of the On Spool Jobs Facility was previously displayed on the operator console.

Control-M monitor stops processing requests from:

Control-O
CMEM subsystem functions
Control-M DO FORCEJOB.

Other parts of Control-M monitor will not be affected.

Corrective Action: Look for previous error messages. Correct the error, shut down the Control-M monitor and start it again.

WKJ442E ERROR WHILE LOADING CTMJOB\CTMMEM FOR CMEM PROCESSING

Explanation: Highlighted, unrollable message.

The CTMJOB or CTMMEM module could not be loaded by the Control-M monitor.

Load for the CTMJOB or CTMMEM module failed for one of the following reasons:

Insufficient storage.
The module or modules could not be found in the libraries specified in the STEPLIB DD statement or in the Linklist.

Control-M monitor will not process requests from:

Control-O
CMEM subsystem functions
Control-M DO FORCEJOB

Corrective Action: Correct the error, shut down the Control-M monitor and start it again.

WKJ443E OPEN ERROR OCCURRED DURING CMEM PROCESSING, DSN=dsn

Explanation: The Control-M monitor has encountered an open error while processing CMEM or Control-O requests.

An open error occurred on one of the Control-M communication data sets. Possible causes are:

An incorrect communication file was defined.
A security product failed the open request.

Control-M monitor stops processing CMEM or Control-O requests.

Corrective Action: Do the following:

Check that CTMPARM points to the correct communication file.
Check the communication file dsn, and make sure that it is properly defined, formatted and cataloged.
Make sure that no restrictions are imposed by MVS, a security package, and so on.
Correct the error, shut down the Control-M monitor and start it again.

WKJ444E I/O ERROR OCCURRED DURING CMEM PROCESSING, DSN=dsn

Explanation: The Control-M monitor has encountered an I/O error while processing CMEM/Control-O requests.

An I/O error occurred on one of the Control-M communication data sets.

Control-M monitor stops processing CMEM/Control-O requests.

Corrective Action: Do the following:

Check the communication file dsn, and make sure that it is properly defined and formatted.
Check that CTMPARM points to the correct communication file. If the file and CTMPARM appear correct: a. Check the MVS LOGREC file for a physical disk error. b. Reallocate and reformat the communication file dsn. After correcting the error, stop the Control-M monitor and start it again.

WKJ445E DYNAMIC ALLOCATION ERROR, RC=rc, REASON CODE=rsn, DSN=dsn

Explanation: The Control-M monitor has encountered a dynamic allocation error while processing CMEM or Control-O requests.

A dynamic allocation error occurred on one of the Control-M communication data sets. Possible reasons for this failure include:

The communication file dsn is not cataloged on the correct disk.
The communication file dsn is cataloged in a catalog which cannot be accessed by the Control-M monitor.
The wrong communication file name, or no communication file name, was specified in IOACPRM.
The MVS allocation exit failed the allocation request.
A security product failed the allocation.

For information regarding the return code rc and the reason code rsn, see the IBM manual MVS Programming: Authorized Assembler Services Guide. Reallocate and format or re-catalog the file if necessary.

The Control-M monitor stops processing CMEM or Control-O requests.

Corrective Action: Check the definitions in IOACPRM and correct as necessary. After the error is corrected, stop the Control-M monitor and start it again.

WKJ446W SYSPLEX TABLE MISSING - SYSTEM LOGGER INTERFACE DISABLED

Explanation: Control-M attempted to read the Sysplex Table and failed.

Control-M could not find the Sysplex Table or encountered errors while reading the Sysplex Table. This could be due to one of the following:

Sysplex Table not present in the STEPLIB concatenation of load libraries.
Sysplex Table has an invalid internal format.
Sysplex Table has no valid, active table entries.

Control-M attempts to allocate, open and use the subsystem-to-monitor (S2M) communication files to implement CMEM-Control-M communication.

Corrective Action: Check why the Sysplex Table is not in the load library or has an invalid format. Correct the problem and recycle Control-M.

WKJ447E SYSTEM LOGGER REQUEST req FAILED: R15=r15 RETURN=rc REASON=rsn

Explanation: A System Logger request failed.

One of the following System Logger requests failed:

Request	Explanation
DEFCFS, IXGINVNT	(define coupling facility structure)
DEFLGS, IXGINVNT	(define log stream)
CONLGS, IXGCONN	(connect to log stream)
WRITEL, IXGWRITE	(write a log stream log block)
BRWSEL, IXGBRWSE	(browse a log stream log block)
DELETL, IXGDELET	(delete a log stream log block)
DISLGS, IXGCONN	(disconnect from log stream)
DELLGS, IXGINVNT	(delete log stream)
DELCFS, IXGINVNT	(delete coupling facility structure)

R15 is provided by Control-M and is one of the following:

R15	Explanation
08	Minor System Logger request error
12	Intermediate System Logger request error
16	Major System Logger request error
20	Permanent System Logger request error
24	Internal Control-M error
28	Operating system does not support System Logger interface
32	Internal Control-M error

The return code rc and the reason code rsn are documented in the IBM manual MVS Programming: Assembler Services Reference. Check that publication for the system action relevant to the return code and reason code in the message. Each System Logger request is in a separate section of the guide. The return and reason codes are described in the topic “Return and Reason Codes” for each System Logger request.

Corrective Action: When a System Logger error occurs, check the system log or the console that displays error messages for the IXGLOG System Logger address space for further details. If the problem persists, prepare the Control-M monitor full output and contact BMC Customer Support.

WKJ448E CMEM LOST num TRANSACTIONS FROM THE CPU WITH SMFID=smfid

Explanation: Control-M was down, or stopped processing CMEM or Control-O requests.

During the time the Control-M monitor was inactive (due to a problem or daily maintenance), the CMEM subsystem functions or Control-O wrote to the Communication files more records than size allowed. Therefore the oldest CMEM or Control-O requests were overwritten and lost.

No additional action is performed.

Corrective Action: To prevent this situation from recurring, do one of the following:

Make sure that the Control-M monitor will not remain inactive for a long time.
Increase the size of the Communication files.

WKJ449E MISSING TABLE tableName IN lib

Explanation: Table tableName was not found in the library lib, or the table was empty.

A FORCEJOB request for a scheduling table or a specific job failed.

This message is followed by message WKJA59E, which contains more details about the error.

This message may also be issued in the following situations:

the library in which the member resides is being compressed
the disk volume on which the library resides on is being reorganized or defragmented

These actions should be avoided during job ordering periods.

No additional action will be taken for the failed job or table order.

Corrective Action: Check that the table exists in the indicated library. Refer to message WKJA59E for further actions.

WKJ44AI SYSTEM LOGGER INTERFACE ACTIVATED

Explanation: This information message indicates that Control-M has successfully initialized the System Logger interface. Control-M can now begin communicating with CMEM.

Corrective Action: No action is required.

WKJ44BE SYSTEM LOGGER NOT SUPPORTED ON THIS OPERATING SYSTEM

Explanation: Control-M cannot utilize the System Logger interface on the host operating system.

The host operating system does not support the System Logger interface.

The CMEM facility is deactivated.

Corrective Action: Change the parameters in the appropriate IOA PARM library members to use the Subsystem-to-Monitor (S2M) communication files to implement communication between CMEM or Control-O and Control-M.

WKJ44CI ATTEMPTING TO RECONNECT TO MVS SYSTEM LOGGER

Explanation: Control-M has detected an MVS System Logger error, and is attempting to reconnect to the MVS System Logger.

Control-M tries several times to reconnect to the MVS System Logger.

Corrective Action: No action is required.

WKJ44DE ATTEMPT TO RECONNECT TO MVS SYSTEM LOGGER FAILED

Explanation: Control-M detected an MVS System Logger error, and attempted several times to reconnect to the MVS System Logger, without success.

Corrective Action: No action is required.

WKJ44EE MVS SYSTEM LOGGER ERROR - CMEM FEATURE DISABLED

Explanation: Control-M detected an MVS System Logger error. Either this error was so severe as not to be recoverable, or Control-M attempted several times to reconnect to the MVS System Logger, without success.

Control-M has stopped attempting to reconnect to the MVS System Logger. The CMEM facility is deactivated.

Corrective Action: If and when the MVS System Logger becomes operational, stop and restart the Control-M monitor.

WKJ44FI TRIGGER JOB jobName (jobId) FOUND ON AJF. JOB NOT FORCED

Explanation: This information message refers to a Control-O or CMEM ON JOBARRIV or ON JOBEND rule with a DO FORCEJOB command. The job used to trigger this DO FORCEJOB was found on the Active Jobs file.

Control-M does not order and submit the DO FORCEJOB.

Corrective Action: No action is required.

WKJ44GA REPLY "ABORT", "CONTINUE", OR "RETRY"

Explanation: After displaying a CMEM-related error message, Control-M disables communication between CMEM or the Control-O monitor and Control-M. Control-M then displays message CTM44GA giving the user the choice of how to continue.

The subtask is suspended until a response to this message is received.

Corrective Action: Enter one of the following responses:

ABORT - terminate the Control-M monitor
CONTINUE - disable communication between CMEM or the Control-O monitor and Control-M, but allow the Control-M monitor to continue processing
RETRY - retry the failed dynamic allocation request

Parent Topic

WKJ messages