6.2 Managing the status of automated actions

When an automated action is executed, the processing is carried out through JP1/IM - Manager and JP1/Base. JP1/IM manages the processing in its domain as the action status.

The following figure shows in diagrammatic form the status transition of an automated action.

Figure 6‒2: Status transition of an automated action

The flow of processing is always from JP1/IM - Manager to JP1/Base on the manager, and then from JP1/Base on the manager to JP1/Base on the target host. When the processing is successful, the status transition is Send, Queue, Running, and Ended, in that order. When the send buffer to JP1/Base is full, the status transition is Wait, Send, Queue, Running, and Ended, in that order. If an error occurs, the action status is set to Fail or Error, and processing terminates.

In the following cases, the status of the automated action is Deterrent or blank, and the processing terminates within JP1/IM - Manager:

Suppress is set and the automated action meets the specified suppression conditions.

In this case, the status of the automated action is set to Deterrent, and processing terminates without the command being executed (for details, see 6.4.4 Suppressing identical actions).
An execution condition has been set for the automated action, but the action definition (command to be executed) has not been set.

In this case, the automated action is executed, but because there is no command to execute, its status is blank and processing ends.

An automated action can be canceled while its status transition is still in progress (Wait, Queue, or Running status), but not while in Send status. The following figure shows the status transition when an automated action is canceled.

Figure 6‒3: Status transition when an automated action is canceled

When an action in Wait, Queue, or Running status is canceled unsuccessfully, it remains in the same status instead of shifting to Cancel or Kill.

When an action in Send status is canceled unsuccessfully, its status becomes Send (Miss).

When a cancellation request is issued for an action in Send status, the deletion processing is not performed until the action execution request is queued in JP1/Base on the target host. Depending on the action status when the cancellation request reaches JP1/Base, the cancellation processing might fail. If the action has reached Ended or Error status, cancellation fails.

The following table describes details about action statuses.

Table 6‒1: List of automated action statuses
Status	Description
`Wait`	Because the send buffer^#1 is full, JP1/Base declined the execution request from JP1/IM - Manager, which is now waiting to retry. (This status is cleared as soon as the buffer becomes available.)
`Send`	The execution request from JP1/IM - Manager is being sent from JP1/Base on the manager to JP1/Base on the target host.
`Queue`	The execution request from JP1/IM - Manager is queued in JP1/Base on the target host. If this status persists for some time, the following problem might have occurred in JP1/Base: More automated actions are being generated than anticipated at the system design stage, leading to a massive backlog of redundant actions in the queue. In this situation, you can cancel the redundant automated actions using the JP1/IM cancellation function (for details, see 6.7 Canceling automated actions).
`Running`	The execution request from JP1/IM - Manager is being executed by JP1/Base on the target host. If this status persists for some time, the following problem might have occurred in JP1/Base: A command executed by a previous automated action has hung or is taking longer than expected to complete. Subsequent automated actions cannot be executed for that reason. In this situation, you can cancel the automated action that caused the problem using the JP1/IM cancellation function (for details, see 6.7 Canceling automated actions).
`Ended`	The command has completed execution in JP1/Base, and the action result has been reported to JP1/IM - Manager. The action result has already been logged to the action re-execution file at startup of the automatic action service. This status is not affected by value of the result code (`E.RESULT_CODE`).
`Fail`	An error occurred before the execution request was passed to JP1/Base. The reason is: An internal error occurred in the automatic action service; JP1/Base (command execution management) that performs the processing is inactive; or No host has been registered in the business or monitoring group specified as the execution target host.
`Error`	An error occurred in processing at the JP1/Base side, and command execution failed. In this situation, the text of the message (KAVB`xxxx`-E) output by JP1/Base is passed to JP1/IM - Manager as the action result. For the texts of the messages output by JP1/Base, see 2.3 Messages related to command execution (KAVB2001 to KAVB2999) in the manual JP1/Integrated Management 2 - Manager Messages.
`Deterrent`	A JP1 event met the condition for executing the automated action, but it occurred within the specified suppression time. Therefore, the action was suppressed (for details, see 6.4.4 Suppressing identical actions).
(blank)	An automated action with a set execution condition, but without a set action definition (command to be executed), has been executed.
`Wait` `(Canceling)`	Cancellation processing is being executed for an automated action in `Wait` status (the cancellation processing is incomplete).
`Send` `(Canceling)`	Cancellation processing is being executed for an automated action in `Send` status (the cancellation processing is incomplete).
`Queue` `(Canceling)`	Cancellation processing is being executed for an automated action in `Queue` status (the cancellation processing is incomplete).
`Running` `(Canceling)`	Cancellation processing is being executed for an automated action in `Running` status (the cancellation processing is incomplete).
`Cancel`	An automated action was canceled before it reached `Running` status.
`Kill`	An automated action was canceled (killed) while in `Running` status.
`Wait` `(Miss)`	An automated action was canceled while in `Wait` status, but the processing failed.
`Send` `(Miss)`	An automated action was canceled while in `Send` status, but the processing failed. Or, an automated action was canceled unsuccessfully while in the previous status (`Wait`), and then shifted to `Send` status.
`Queue` `(Miss)`	An automated action was canceled while in `Queue` status, but the processing failed. Or, an automated action was canceled unsuccessfully while in a previous status (`Wait` or `Send`), and then shifted to `Queue` status.
`Running` `(Miss)`	An automated action was canceled while in `Running` status, but the processing failed. Or, an automated action was canceled unsuccessfully while in a previous status (`Wait`, `Send`, or `Queue`), and then shifted to `Running` status.
`Ended` `(Miss)`	An unsuccessfully canceled action is in `Ended` status.
`Error` `(Miss)`	An unsuccessfully canceled action is in `Error` status.
`Unknown`^#2	The execution result of an automated action cannot be verified because a problem of some sort has caused inconsistencies in the files containing execution results (action information file, action hosts file, and command execution log file). In this case, you must delete the files. Once these files are deleted, the execution results of past automated actions cannot be referenced. For the deletion procedure, see 11.5.1(10) Actions to take when Unknown is displayed as the automated action execution status in the JP1/Integrated Management 2 - Manager Administration Guide.

#1: The buffer used when sending a request to execute an automated action from JP1/IM - Manager to JP1/Base on the manager.

#2: This is not an action status, but indicates that JP1/IM - Manager was unable to acquire the status of the automated action.

When the automated action definition is disabled, the action is not executed. That is, the status does not change and thus the action status is not stored in the action information file.

You can check the execution status of an automated action in JP1/IM - View or by executing a command. For details, see 6.6 Checking the execution status and results of automated actions.

To Page Top