Previous Topic

Next Topic

Book Contents

Book Index

Messages WKJC00 through WKJCxx

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.

WKJC39E action FAILED FOR cond

Explanation: An error occurred while processing a request to add or delete the condition.

The source of the request may be:

This message is preceded by another message, which gives more details of the cause of the error.

No additional action will be taken for the failed add or delete condition request.

Corrective Action: Correct the error as detailed in the preceding message. If addition or deletion of the condition is still required, it should be added or deleted manually. If the specification in the original request was incorrect, correct it and reload if necessary. Reload the CMEM table or recorder the Control-O rule.

WKJC50E INSUFFICIENT STORAGE FOR CMEM PROCESSING

Explanation: Highlighted, unrollable message.

Insufficient storage for CMEM processing initialization in the Control-M monitor.

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

Corrective Action: Increase the REGION size specified for the Control-M monitor.

WKJC50W Control-M MONITOR CMEM FACILITY IS NOT INSTALLED

Explanation: Control-M has determined that the CMEM facility is not installed.

Communication between CMEM or the Control-O monitor and Control-M is not established, but the Control-M monitor continues processing.

Corrective Action: No action is required.

WKJC51E INSUFFICIENT STORAGE FOR TABLE tableName FROM lib

Explanation: Insufficient storage for loading table tableName into storage.

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

Job order fails. No additional action taken.

Corrective Action: Increase the REGION size specified for the Control-M monitor; or define a smaller table if possible, for example, if only one job is ordered from the table. For further actions, see message WKJA59E.

WKJC52E DATASET IS NOT A LIBRARY, DSN=dsn

Explanation: While processing a CMEM/Control-O request, the Control-M monitor encountered a data set dsn which is not a partitioned data set.

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

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

Corrective Action: Specify the name of a partitioned data set containing one or more valid scheduling tables.

WKJC53E DATASET IN USE, DSN=dsn

Explanation: While processing a CMEM/Control-O request, the Control-M monitor encountered a data set dsn which is currently used by another job.

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

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

Corrective Action: Determine which job has allocated the data set with disposition OLD and resolve the conflict.

WKJC54E DATASET IS NOT CATALOGED, DSN=dsn

Explanation: While processing a Control-M DO FORCEJOB, CMEM or Control-O request, the Control-M monitor encountered a data set dsn which is not cataloged.

This message is followed by additional messages which identify the failed action.

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

Corrective Action: Make sure that the SCHLIB library specified in the CMEM table entry refers to a cataloged data set.

WKJC55E DYNAMIC ALLOCATION ERROR, DSN=dsn

Explanation: While processing a CMEM or Control-O request, the Control-M monitor encountered a dynamic allocation error.

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

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

Corrective Action: Record the problem, prepare the Control-M monitor full output, and contact BMC Customer Support.

WKJC56E M2S FILE IS FOR QNAME qName. IT DOES NOT MATCH IOA QNAME qName DSN=dsn

Explanation: Control-M could not allocate the monitor to the Monitor to Subsystem (M2S) file of another IOA environment.

During initialization the Control-M monitor compares the QNAME in the IOA environment with the QNAME in the M2S file. They should match.

Message CTM441E is issued.

Corrective Action: Check the IOACPRM member and do one of the following:

WKJC57E S2M FILE IS FOR SMFID smfid QNAME qName. IT DOES NOT MATCH IOA QNAME qName DSN=dsn

Explanation: The Control-M monitor could not allocate the subsystem to the Subsystem to Monitor (S2M) file of another IOA environment.

During initialization the Control-M monitor compares the qname in the IOA environment with the qname in the S2M file. They should match.

Message CTM441E is issued.

Corrective Action: Check the CTMPARM member and do one of the following:

WKJC58I M2S FILE FOR IOA QNAME qName. DSN=dsn

Explanation: This information message identifies the Monitor-to-Subsystem (M2S) file that the Control-M monitor allocated for communication with the Control-O or the CMEM monitor.

qName is defined in the M2S file with the data set name dsn.

Corrective Action: No action is required.

WKJC59I S2M FILE FOR SMFID smfid QNAME qName DSN=dsn

Explanation: This information message identifies the Subsystem-to-Monitor (S2M) file that the Control-M monitor allocated for communication with the Control-O or the CMEM monitor.

qName is defined in the S2M file with the data set name dsn.

Corrective Action: No action is required.

WKJC5AE SMFID smfid NOT FOUND IN M2S DSN=dsn

Explanation: The SMFID is not in the Monitor-to-Subsystem (M2S) file.

During initialization the Control-M monitor checks that every SMFID required for CMEM functions is defined in the M2S file.

Message Control-M issues the CTM441E message and CMEM functions becomes inactive.

Corrective Action: Add the missing SMFID to the M2S file, and restart the Control-M monitor.

For more information on adding the SMFID to the M2S file, see the section on reformatting communication files for only one SMFID in the INCONTROL for z/OS Installation Guide.

WKJC5BE INVALID BLOCK SIZE FOR FILE TYPE type

Explanation: The record length of the communication file between Control-M and CMEM was incorrect. The record size for the file was defined incorrectly. As a result, no records are written to the file.

The file type is either M2S or S2M:

Job processing continues, but CMEM processing is ignored.

Corrective Action: Reformat the file with the correct record size.

Parent Topic

WKJ messages