2.8.3 Execution status of local actions
A local action is set by default to start automatically when the system is started. If you start a local action, the JP1 events registered on the local host are acquired, and the JP1 event is compared to the conditions that have been specified in the local action execution definition file. If the acquired JP1 event matches the conditions, the corresponding command will be executed. Note that the JP1 event is compared to the conditions in the order in which they were defined in the local action execution definition file. In the local action execution definition file, you should define conditions in the order of priority.
You can check the execution status of local actions by using the jbslistlcact command. There are two types of execution statuses: "waiting" and "running". You can cancel the action in either of these statuses. The changes that the execution status goes through from the execution condition of the local action being satisfied to the completion of the executed action is notified by using JP1 events and the local action execution log file.
The following figure illustrates the execution status of local actions.
|
|
![[Figure]](GRAPHICS/ZU012450.GIF)
You can control the number of local actions waiting or running by using the following functionalities.
- Organization of this subsection
(1) Preventing the same action from executing
Using this functionality, you can prevent the same action from executing multiple times over a set time period. This is useful for an action that is normally executed once only over a set time period (for example, when sending an email to the system administrator). While this functionality is enabled, the same action will not go to the waiting status, even if a condition is satisfied.
(2) Limiting the number of waiting actions
Using this functionality, you can specify a limit on the number of actions waiting. When the number of actions waiting exceeds the specified limit, any action goes to the waiting status, even if a condition is satisfied.
(3) Limiting the number of concurrently executing actions
Using this functionality, you can specify a limit on the number of actions that can be executed at the same time. The actions will be executed only when the number of actions being executing at the same time does not exceed the specified limit. When the limit is exceeded, the actions will go to the waiting status.