The KILLTASK
statement enables users to terminate one or more tasks or server sessions
that are executing asynchronously. The KILLTASK statement is
useful only for an asynchronous RSUBMIT.
Note: KILLTASK should
be used for asynchronous tasks that seem to be hung or to be having
a problem. KILLTASK ends the server session. However, do not substitute
KILLTASK for SIGNOFF. Use SIGNOFF to terminate server sessions that
are functioning normally.
KILLTASK
causes any log or output lines, as applicable, that have accumulated
in the backing store to be sent to the parent Log and Output windows.
Before the data is sent to the parent Log and Output windows, this
message is displayed:
NOTE: Process TASK1 was terminated by KILLTASK statement.
KILLTASK
removes the specified task from the list of active tasks and from
the LISTTASK output. If KILLTASK is executed for a completed task,
this message is displayed and the task will not be terminated:
NOTE: Transaction TASK2 was not killed because it is not running asynchronously.
Task termination
also deletes the content of the WORK library of the server session.