Job Management Partner 1/Integrated Management - Manager Overview and System Design Guide

5.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).
  When a JP1 event arrives at a JP1/IM manager, it is compared with the action definition parameters and execution conditions in their order of precedence, separately for each parameter group. When an execution condition is satisfied, the action that has the highest precedence in each parameter group is executed.
  Each parameter group is assigned a one-digit number (0 to 9). This number is unrelated to the execution order or precedence of the automated actions.
  If you do not specify the parameter group when defining an automated action, it will belong to parameter group 0.
  
• 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. 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.
  

[Contents][Back][Next]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.