The forced cancel command is used to forcibly cancel a
job by terminating the servant region's Java Virtual Machine (JVM)
in which the job is running. Forced cancel is only supported for batch
and compute-intensive jobs running on the z/OS operating system.
About this task
If a forced cancel is issued against a batch or compute-intensive
job running on the distributed platform, the forced cancel command
has the same effect as the cancel command. Use the forced cancel command
with extreme caution, because it sends an ABEND signal to the servant
region's JVM. If WebSphere security is turned off, forced cancel
is allowed to all job submitters. If WebSphere security is turned
on, forced cancel will NOT be allowed by default. To allow a forced
cancel, you must create a custom property, called AllowedForcedCancelRoles,
in the job scheduler panel in the administrative console.
The AllowedForcedCancelRoles
custom property accepts the following values:
- none
No user is allowed to issue forced cancel command.
- all
All job submitters are allowed to issue forced cancel command
on their jobs.
- <Role_1>, [<Role_2>, ...]
Only the following EJB roles
are allowed to issue forced cancel command.
The following steps show you how to create the custom
property, AllowedForcedCancelRoles, in the job scheduler panel.
Example
Example of commands and their descriptions follow:
Table 1. Commands and their descriptionsDescription |
Command |
Forced cancel on lradmin-ref role |
AllowedForcedCancelRoles="lradmin-ref"
|
Forced cancel on all roles |
AllowedForcedCancelRoles="all"
|
Forced cancel on a set of roles |
AllowedForcedCancelRoles="lradmin-ref, lrsubmitter-ref"
|
Disallow forced cancel at all |
AllowedForcedCancelRoles="none"
|
Use the command-line interface, lrcmd.sh/lrcmd.bat, or
the job management console (JMC) to forcibly cancel a job. The following
line of code is a lrcmd example:
lrcmd -cmd=forcedCancel -jobid=myjob:2 -host=myLRShost -port=9083