Messages WKJA00 through WKJAxx

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.

WKJA56E MEMBER memName READ ERROR RC=rc IN dsn

Explanation: While processing a Control-M DO FORCEJOB, CMEM or Control-O request, the Control-M monitor encountered an error while reading table memName in data set dsn.

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

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

Corrective Action: For a description of return code rc, see the DOCIMEM member in the IOA DOC library.

WKJA57E MEMBER memName IS EMPTY IN dsn

Explanation: While processing CMEM or Control-O request, the Control-M monitor encountered an empty table memName in data set dsn.

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: Make sure that table memName contains valid scheduling information.

WKJA58E ABEND abCode WHILE PROCESSING dsn

Explanation: While processing a CMEM/Control-O request for data set dsn, the Control-M monitor encountered an abend condition abCode.

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: Record the abend code, prepare the Control-M monitor full output, and contact BMC Customer Support.

WKJA59E FORCEJOB FAILED FOR JOB jobName IN TABLE tableName FROM dsn

Explanation: An error occurred while processing a FORCEJOB request for the jobName job, or, in the case where jobName is blank, for the complete scheduling table tableName.

The source of the request may be:

• a Control-O request for a DO FORCEJOB.
• a Control-M request for a DO FORCEJOB.
• a CMEM FORCEJOB action.

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

Control-M may try again to execute the job or table, depending on the values set for the FORCE#RT and FORCE#WI installation parameters. For more information, see the customization chapter of the INCONTROL for z/OS Installation Guide.

Corrective Action: Correct the error as detailed in the preceding message. If scheduling is still required for the job or table for which the error occurred, then the job or table should be ordered manually. If the specification in the original request was incorrect, correct it and reload, if necessary. Reload the CMEM table or reorder the Control-O rule.

WKJA5AE ANOTHER MONITOR ALREADY READING FROM LOG STREAM STR=structureName L/S=logStreamName

Explanation: This error message is issued when an attempt is made to read an MVS System Logger log stream which is currently being read by another Control-M monitor.

To avoid a loop of FORCEJOB jobs, the same MVS System Logger log stream should not be read simultaneously by more than one Control-M monitor. Should a second Control-M monitor attempt to read the same log stream, this error message is issued.

The CMEM facility is deactivated for this Control-M monitor.

Corrective Action: If and when the other Control-M monitor terminates, this monitor can be restarted. Make sure only one Control-M monitor is reading the same MVS System Logger log stream simultaneously.

WKJA5BE FREEMAIN (storage_add /len) FAILED AT POINT ref_point

Explanation: A Control-M component attempted to free a block of working storage, but failed to do so.

The variables in this message are:

• storage_add - the working storage address
• len - the length of the working storage
• ref_point - the reference point in the Control-M component

No additional action is performed.

Corrective Action: If this is a recurring problem, prepare the Control-M monitor full output and contact BMC Customer Support. If ignored, this may cause severe insufficient storage problems.

WKJA5CI CONTROL-M WILL RETRY PERFORMING THE FORCEJOB REQUEST FOR JOB jobName TABLE tableName IN dsn

Explanation: Control-M failed to execute a DO FORCEJOB request because a scheduling table was in use.

The source of the DO FORCEJOB request may be any of the following:

• a Control-O request for a DO FORCEJOB
• a Control-M request for a DO FORCEJOB
• a CMEM DO FORCEJOB action

Control-M queues the DO FORCEJOB request, and may try again to execute it, depending on the values set for the FORCE#RT and FORCE#WI installation parameters.

For more information on the FORCE#RT and FORCE#WI installation parameters, see the customization chapter of the INCONTROL for z/OS Installation Guide.

Corrective Action: No action is required.

WKJA5DI FORCEJOB SUCCEEDED AFTER RETRIES FOR JOB jobName IN TABLE tableName FROM dsn

Explanation: After failing to execute a DO FORCEJOB request because a scheduling table was in use, Control-M retried the request and succeeded in executing it, in accordance with the values set for the FORCE#RT and FORCE#WI installation parameters.

The source of the DO FORCEJOB request was one of the following:

• a Control-O request for a DO FORCEJOB
• a Control-M request for a DO FORCEJOB
• a CMEM DO FORCEJOB action

Corrective Action: No action is required.

WKJA5EI CONTROL-M WILL RETRY PROCESSING DATASET TRIGGER: trigger_dsn

Explanation: During the processing of a CONNECT DIRECT request, no successfully triggered events were processed, and a data set-in-use condition occurred.

The probable source of the CONNECT DIRECT request is the IOADCC utility.

Control-M queues the DO FORCEJOB request, and will try again to execute it, in accordance with the values set for the FORCE#RT and FORCE#WI installation parameters.

For more information on the FORCE#RT and FORCE#WI installation parameters, see the customization chapter of the INCONTROL for z/OS Installation Guide.

Corrective Action: No action is required.

WKJA5FE SCHEDULE LIBRARY schedLib IS MIGRATED

Explanation: A DO FORCEJOB command was issued for a table in the schedLib scheduling library, which has been migrated. An attempt was made to RECALL the library. An additional message follows describing whether the RECALL action was successful or not.

Corrective Action: Look for the following messages, which inform about the success of the RECALL action.

WKJA5GE RECALL OF LIBRARY schedLib FAILED RC rc REASON rsn

Explanation: A DO FORCEJOB command was issued for a table in the schedLib scheduling library, but the action could not be completed because the library, which was migrated, could not be recalled.

Corrective Action: Do the following:

• Ensure that the RECLRQST parameter is set (in the CTMPARM member of the IOA PARM library).
• Check the rc and rsn codes in the section about the IOAMEM assembler macro in the INCONTROL for z/OS Administrator Guide, and take the appropriate action.

WKJA5HI SCHEDULE LIBRARY schedLib HAS BEEN RECALLED

Explanation: This information message indicates that a DO FORCEJOB command was issued for a table in the schedLib scheduling library. To complete this action, the library, which was migrated, has been RECALLed.

Corrective Action: No action is required.

WKJA5IE CONTROL-M WILL NO LONGER RETRY THE REQUEST

Explanation: When a schedule table is not available because the data set is in use by another address space, Control-M retries the request several times based on the FORCE#RT parameter in CTMPARM. When this number of retries is exhausted and Control-M no longer retries the request, this message is displayed.

Control-M no longer retries the request.

Corrective Action: Determine why the data set is in use and retry the request manually. Messages CTMC53E and CTMA59E give details about the job name, table name, and schedule library name.

WKJA5JE POST ERROR NOTIFICATION STAGE stage FAILED

Explanation: A DO FORCEJOB action triggered by this job failed. An attempt to specify the post-error indication in the job image failed.

Corrective Action: Do the following:

• Locate the failed DO FORCEJOB command and manually order the job.
• Notify BMC Customer Support about the error. The stage specified in the message is required for BMC error analysis.