|
|
|
|
|
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 displays the results of a DO RESOURCE action in a Control-O rule. The quantitative resource has been added, deleted, or changed in the Control-M Resources file.
Corrective Action: No action is required.
Explanation: This information message displays the results of a Control-O DO RESOURCE request. The quantity of resource is increased (+) or decreased (-) from old_qty by the amount in delta_qty. If no sign is indicated, the quantity has been set to the amount specified in delta_qty.
The variables in this message are:
Corrective Action: No action is required.
Explanation: The quantitative resource resourceName which was specified in a Control-O DO RESOURCE action does not exist in the Control-M Resources file.
Someone may have deleted the quantitative resource from the Control-M Resources file or it may never have been added.
Corrective Action: Scan the IOA Log to see why the resource may have been deleted. Check that the syntax of the resource in the Control-O DO RESOURCE action is correct.
Explanation: The quantitative resource resourceName specified in a Control-O DO RESOURCE action, cannot be added to the Control-M Resources file because the file is full.
The quantitative resource is not added to the file.
Corrective Action: Contact your systems programmer about the possibility of increasing the capacity of the Control-M Resources file.
Explanation: The Control-O resource action that was requested (add/change) was not performed due to security restrictions at the site.
The resource action is not performed.
Corrective Action: If you think the user that owns the rule should be authorized to issue resource requests, please contact your INCONTROL administrator. You may need to adapt your Control-M security criteria.
Explanation: The information message displays the results of a Control-O DO COND action.
The Control-M monitor adds/deletes the prerequisite condition.
Corrective Action: No action is required.
Explanation: Control-O issued a DO COND request, but the Prerequisite Condition was not added/deleted.
User is not authorized to add/delete this condition from the IOA Conditions file.
Corrective Action: If you think the user that owns the rule should have the authority to perform DO COND actions, contact your INCONTROL administrator. You may need to adapt your Control-M security criteria.
Explanation: The CNDREC# parameter in the IOAPARM member has been changed, but the IOA Conditions file has not been rebuilt.
A difference between the length of the IOA Conditions file and the CNDREC# value specified in the IOAPARM member of the PARM library was detected.
This is usually caused by using the IOAPARM member (read from the IOA Load library) for the wrong monitor.
The Control-M monitor shuts down.
Corrective Action: Correct the problem and restart the monitor.
Explanation: The action specified in a CONTRO-O DO RESOURCE statement failed, because it would have produced an illegal quantity.
Updating the resource would have produced either a negative quantity or a quantity greater than the maximum of 9999. Therefore it was rejected.
The system ignores the illegal statement and continues processing.
Corrective Action: Check and correct, if necessary, the definition of the quantitative resource to be updated and/or the rule defining how to update it.
Explanation: DO RESOURCE statement in Control-M/Operator Rule was ignored by Control-M Monitor because the corresponding Rule was triggered by the message issued from a job submitted by Control -M and the Quantitative Resource (whose name specified in DO RESOURCE) is already allocated to the job by Control-M.
Corrective Action: No action is required.
Explanation: Control-M was unable to perform a job’s DO REMFORCE statement due to insufficient storage allocated to the Control-M monitor.
Corrective Action: Increase the region size of the Control-M monitor.
Explanation: Control-M was unable to perform a job’s DO REMFORCE statement due to an internal error.
Corrective Action: Contact BMC support.
Explanation: Control-M was unable to perform a job’s DO REMFORCE statement due to a problem in accessing the DAM2F file.
Corrective Action: Verify that DAM2F is allocated to a valid file. If it is, contact BMC support.
Explanation: This information message indicates that as a result of a user request, the job or STC is reactivated, and the Control-M monitor searches again for the sysout of the job or STC.
When option A (Reactivate) is specified for a job or STC in the Active Environment screen, the status of that job or STC changes from DISAPPEARED to SUBMITTED, and the Control-M monitor searches again for the sysout of the job to analyze job execution results.
Corrective Action: No action is required.
Explanation: This information message indicates that submission of the job could not be completed because of a temporary problem (for example, data set in use).
This information message accompanies other messages which identify the reason for the submission failure.
Control-M will retry submission later, for a maximum of three attempts. After three attempts to submit the job, the submission is cancelled.
Corrective Action: Check previous error messages. Correct the error and rerun the job.
Explanation: Control-M successfully performed a job’s DO REMFORCE statement. The unique ID can be used to track the remote force request on the remote Control-M.
Corrective Action: No action is required.
Parent Topic |