CANCEL Command

The CANCEL command deletes jobs from the CA Workload Automation SE queues.

For CPU jobs, the CANCEL command only removes the job from the CA Workload Automation SE queues. Cancellation of a job in the CA Workload Automation SE active queue or ready queue (if it has been submitted) does not cause termination of the job's execution. CPU jobs that can be executing have to be canceled from the operating system separately. Execution must be terminated from an OS system console.
For XPJOB jobs, the CANCEL command removes the job from the CA Workload Automation SE queues. If the initialization option XPDEF, XPKILL is set to YES, and the XPJOB job has been submitted to the target node but is still in the ready queue or the active queue, a cancel request is created and sent to the target node. Some remote CA Scheduling Agents support the cancel request, and the request cancels or "kills" the process execution. It is not the responsibility of CA Workload Automation SE to verify that the target platform supports the kill facility. If the cancel request was not transmitted, an error message appears in the browse and log data.
For agent definition jobs (AGJOBs), the CANCEL command sends a request to the agent and removes the job from the CA Workload Automation SE queues. If the agent is not active at the time of the CANCEL request, the message is queued and sent when the agent becomes active.

If the initialization option XPDEF, XPKILL is set to NO, the XPJOB is canceled from the CA Workload Automation SE queues, and no cancel request is sent to the target platform. To view the XPKILL option, enter the command /DISPLAY,ST=XPS.

This function is available on the QM.1, QM.6, and QM.7 panels as option C. The CANCEL command has three formats, depending on the queues in which the task resides.