6.3.3 Parameter groups and AND condition

By using parameter groups and AND conditions, you can set complex conditions for executing automated actions.

• Parameter groups

  A parameter group is a set of judgment conditions for executing an automated action. There are 10 parameter groups. Each automated action definition belongs to one parameter group only.

  You can use parameter groups to execute multiple actions in response to one event, or to associate multiple execution conditions using an AND condition (as explained later). A parameter group is specified with one-digit number (0 to 9).

  If a JP1/IM manager receives a JP1 event, the JP1/IM manager compares the JP1 event with the execution conditions of the action definition parameters for each parameter group, from the parameter group with the smallest number to the parameter group with the largest number. Only one automated action is executed for a JP1 event for each parameter group.

  If multiple execution conditions match an event in a parameter group, only the action definition parameter with the highest priority is executed (as explained in 6.3.2 Precedence of execution conditions).

  If multiple action conditions match a JP1 event, command execution requests are issued to the JP1/Base in the order the comparison of the action conditions is performed. However, command execution requests might not be performed in order if execution requests are issued to multiple hosts or if two or more commands are executed concurrently.

• AND condition

  An AND condition is a setting that requires all the execution conditions to be satisfied before an action is executed.

  When an ampersand (&) is specified instead of a number in a parameter group specification, the relationship with the preceding execution condition in the automated action definition (displayed one line above in the GUI, or written one action block above in the definition file) is handled as an AND condition. You can define a maximum of 10 automated action definitions joined by an AND condition.

  When a received event matches one of the execution conditions joined by an AND condition, it waits for another event matching another execution condition to be received. When all the execution conditions joined by the AND condition are satisfied, the automated action is executed.

  However, disabled automated action definitions are not evaluated to determine whether to execute the automated action.

  You can specify an AND-event keep limit as a timeout for the AND condition to be satisfied. If the required JP1 event arrives after expiry of the AND-event keep limit, it does not satisfy the AND condition.

  Note that when the event base service (evflow process) stops, all events waiting for an AND condition to be satisfied are discarded. Take care if the system is restarted, by process management after an error, for example, or in a cluster system when a failover occurs.

When DESC_VERSION of the automated action definition file (actdef.conf) is 4, with one of the operations listed below, you can ensure that the status of a satisfied AND-joined condition remains the same unless the automated action definition of the conditions is changed.

• In the Action Parameter Definitions window, select the Retain the conditions for which the definition was not changed check box and click the Apply button.

• Execute the jcachange command with the -on, -off, -e, or -st option specified.

When DESC_VERSION is 3 or earlier or when you use any way other than those listed above to update the action definition, the status (satisfied or unsatisfied) of every AND-joined condition is initialized.

To Page Top