|
Entire document Available as PDF |
Table of Contents
To prevent the wrong jobs from being cancelled and to reduce operator distractions, operators have been instructed NOT to cancel jobs for users.
You can submit a batch job that uses the RELEASE utility to cancel a previously submitted job that is not yet in execution. The RELEASE utility is documented in Utilities: RELEASE (D0070).
The RELEASE utility has the following restrictions:
You cannot cancel a job belonging to someone else. The RELEASE utility job must be submitted with the same userid as the job to be cancelled.
Only jobs awaiting execution can be cancelled. A job in execution or awaiting print cannot be cancelled.
If several jobs from the same account have the same name, you must use the job number to identify the job instead of using the name.
If these restrictions are not met, the "JOB NOT FOUND" message will be written.
We recommend using CLASS=5 on a cancellation job because the cancellation job must execute before the job to be cancelled enters execution.
You can also cancel jobs from an interactive workstation by signing on to TSO.
If you are signed on to TSO, you can use the CANCEL or PURGE command to cancel a job. You must be signed on to TSO under the userid used to submit the job. The CANCEL command requests that
JES2 terminate the scheduling or execution of a job. The output will say that the job was cancelled. The PURGE command requests that JES2 purge a job from the execution, print, or fetch queue. No output will be printed. If the job is
executing at the time you issue the PURGE command, the job will finish executing and then the output will be deleted. If you want a job to be cancelled immediately and its output purged, you must issue both commands. The format for the
two commands is as follows:
CANCEL JOB(jobnameornnnnn)PURGE JOB(jobnameornnnnn)
Use either the job name or the job number () of the job to be cancelled or purged; do not use them together in the same command.nnnnn