|
|
|
|
|
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.
Explanation: This information message indicates that the Priority Propagation process has been started by the Control-M monitor.
Corrective Action: No action is required.
Explanation: This information message indicates that the Priority Propagation process has ended.
Corrective Action: No action is required.
Explanation: The Control-M monitor did not have enough storage for either the Deadline Scheduling Calculation process or for the Priority Propagation process.
The process is aborted.
Corrective Action: Increase the storage for the Control-M monitor.
Explanation: The Control-M monitor cannot access a file because it is being used by another component. The monitor requires exclusive access to the file.
The monitor waits for the file to be released.
Corrective Action: Check who is holding the file and have it released.
Explanation: The Dependencies file allocated to the Control-M monitor does not belong to the current installation.
The process is aborted.
Corrective Action: Verify that the correct Dependencies file is allocated to the Control-M monitor through the DAGRAPH DD statement.
Explanation: This information message is issued when the Priority Propagation process ends. The message indicates the number of jobs that received higher priority, and the number of jobs whose priority was not changed, that is, were held.
Corrective Action: No action is required.
Explanation: This information message indicates that a request to resolve all deadline scheduling requests was received either from a modify command, or from a user entering command REFRESH in the Jobs Dependencies screen.
The Control-M monitor resolves all deadline scheduling definitions.
Corrective Action: Wait for message JDLK47I or CTMK47I, to signal the end of the process.
Explanation: This information message indicates that the Control-M monitor successfully finished resolving all deadline scheduling definitions. This message is accompanied by message JDLK48I or CTMK48I which displays the number of updated jobs.
Corrective Action: No action is required.
Explanation: This information message indicates that the Control-M monitor successfully finished resolving all deadline scheduling definitions.
The variables in the message are:
This message follows the JDLK47I message.
Corrective Action: No action is required.
Explanation: A request has been made to resolve deadline scheduling, but the Deadline Scheduling Facility has not been enabled in the Control-M defaults member.
Deadline scheduling is not performed.
Corrective Action: Ask your INCONTROL administrator to enable the Deadline Scheduling Facility in the Control-M default parameters member.
Explanation: A job or group entity that produces an out-condition that acts as an in-condition for the job being processed was not found in an internal table. This internal error was detected during the processing of the REFRESH DEADLINE (deadline scheduling) command while it was analyzing a group entity and its component jobs.
The REFRESH DEADLINE command is aborted.
Corrective Action: Contact your INCONTROL representative for assistance. Have the complete job log and the output of the Control-M monitor address space available.
Explanation: An internally-created cross-reference table used for group processing was missing when the REFRESH DEADLINE (deadline scheduling) command was analyzing a group entity and its component jobs.
The REFRESH DEADLINE command is aborted.
Corrective Action: Contact your INCONTROL representative for assistance. Have the complete job log and the output of the Control-M monitor address space available.
Explanation: This information message indicates that the Dependencies file was successfully formatted and is ready for use. The current dependencies between jobs can be viewed after entering the REFRESH command from the appropriate screen.
Corrective Action: No action is required.
Explanation: A REFRESH command was issued to the Control-M monitor with an unrecognizable parameter.
The REFRESH command is not executed.
Corrective Action: Check the command syntax and reissue the command.
Explanation: A REFRESH DEADLINE command was submitted with parameters. However, this command does not take any parameters.
The command is not executed.
Corrective Action: Delete the parameters and resubmit the command.
Explanation: The number of prerequisite conditions for dependency calculations exceeds the maximum number supported. The maximum number of conditions is ten times the maximum number of records in the Active Jobs file.
The dependency calculation process is aborted.
Corrective Action: Increase the size of the Active Jobs file.
Explanation: This information message is issued to the IOA Log file after the Job Dependencies file is updated.
Corrective Action: No action is required.
Explanation: The Control-M monitor encountered an internal error during REFRESH processing in the Control-M Active Environment screen.
The system produces a diagnostic dump, and continues processing.
Corrective Action: Ask your system programmer to record the error message, the diagnostic dump, and the Control-M monitor full output; and contact BMC Customer Support.
Explanation: The user specified invalid parameters for operator command SDOUT.
The operator command is ignored.
Corrective Action: Specify valid parameters for operator command SDOUT. See the Control-M chapter of the INCONTROL for z/OS Administrator Guide for a details about this operator command.
Explanation: This information message is issued after successful execution of operator command SDOUT.
The variables in this message are:
Corrective Action: No action is required.
Parent Topic |