5.7 Canceling automated actions
You can cancel automated actions whose status is any of the following:
-
Wait, Queue, or Running
-
Send (Miss)#, Wait (Miss)#, Queue (Miss)#, or Running (Miss)#
#: Before you cancel an automated action in a status tagged (Miss), you should identify and fix whatever caused the cancellation failure (Miss), by examining the execution result in detail (error log) or by conducting an event search to check what happened on the target host, for example.
When you cancel an automated action, its status is tagged as (Canceling), and then becomes Cancel or Kill. If the cancellation processing fails, the action status is tagged as (Miss), and then proceeds through the usual status transitions (for details, see 5.2 Managing the status of automated actions).
You can cancel an automated action and check whether cancellation was successful using the following:
-
List of Action Results window, Action Log window, and Action Log Details window (cancel only) in JP1/IM - View
-
jcacancel command (cancel), jcashowa command (cancellation status check)
- Range of actions that can be canceled
-
Only actions issued from the manager on which you are executing the cancellation processing can be canceled. That is, actions issued from a base manager cannot be canceled from the integrated manager.
The following figure shows the range of actions that can be canceled.
Figure 5‒7: Range of actions that can be canceled ![[Figure]](GRAPHICS/CS036600.GIF)
As shown in the figure, when action cancellation processing is executed from the integrated manager, only those action issued from the integrated manager are affected. Because actions executed from the base manager are not affected, they are processed as usual on the agent. To cancel actions issued from the base manager, you must execute the cancellation processing from that host.