It is possible for a looping CICS® task or shortage
of CICS resources to bring all normal processing in a CICS region to a halt. The KILL option helps you to remove such
tasks more quickly from a CICS region, with the minimum
impact on the integrity of your systems.
About this task
You must use the KILL option only when it becomes impossible for you to cancel the task or tasks
by using any of the standard CICS mechanisms. The KILL option
does not guarantee integrity of any kind, but in some situations allows you to free a
stalled region, enabling the region to continue processing.
Procedure
- Try to cancel the task using the PURGE or FORCEPURGE option on the CEMT SET
TASK command. Both PURGE and FORCEPURGE might enable you to remove the task, retaining system and data
integrity. If neither PURGE or FORCEPURGE respond within a reasonable time, use the KILL
option.
- Use the KILL option on the appropriate command, depending on what task you are trying to
cancel. The KILL option is available on CEMT SET TASK, CEMT SET
CONNECTION, and CEMT SET TERMINAL commands.
- If you cannot list the active tasks in the system to determine which task or tasks should be
canceled, use the CEKL transaction.
- Enter the command CEKL INQUIRE TASK to list information about tasks in
the CICS region; for example, all tasks that are suspended.
- Enter the command CEKL SET TASK to cancel a selected task using the
PURGE, FORCEPURGE or KILL option.
- Having identified the problem task, you can then use the normal process of attempting to remove
the task from your system using either PURGE or FORCEPURGE through the CEMT SET TASK (value) PURGE
transaction. Initially you can track the state of the task to see if it has successfully removed. Two
things might have happened:
- The task was not purged within an acceptable length of time.
- The CEMT transaction did not respond.
If CEMT is unavailable, consider using the CEKL command outlined in step 5.
Important: If the task could not be purged but CEMT is available, see step 6 before trying to using the KILL
option. You must try FORCEPURGE before using KILL.
- You can identify problems in your system using the CEMT transaction or CICSPLEX SM. However, if
these are unavailable or not running (because the QR TCB is looping or suspended), you can use the
new command, CEKL. You can use the CEKL command to do the following:
- To identify the problem tasks.
- To remove the tasks by executing the PURGE, FORCEPURGE, or KILL option.
- To monitor the effects of attempting to remove the tasks from your system.
For full details about CEKL, see CEKL.
- If you use the KILL option, an abend code is issued that reports the protective state of the
task (purge or forcepurge protection) when it was killed. Regardless of the state of the transaction
KILL cannot guarantee any data or system integrity.
DANGER
This action can result in unpredictable effects, including overwriting of data
within the CICS region or abnormal termination of the CICS region. It should only be used as a last resort.
Using CEMT (or equivalent SPI commands), you are not allowed to kill a task without having first
attempted to forcepurge it. You can use CEKL to kill the task without having first forcepurged it.
Use CEKL is very much the option of last resort.
Removing tasks can have an effect on the integrity of your system. The following table shows the
possible consequences of using purge, forcepurge, or kill.
Table 1. Data and system integrity| Command |
System integrity |
Data integrity |
| PURGE |
YES |
YES |
| FORCEPURGE |
YES |
NO |
| KILL |
NO |
NO |
CICS ignores a request to purge a task if the task is
marked non-purgeable. CICS might ignore or delay processing a
request because of a risk of damaging CICS system integrity,
for example, because I/O might still be in progress to a buffer owned by the task, or because
recovery processing would be unable to complete.