Creating more complex Rules
The following examples show how to create Rules using other features of the Rule Processor, such as the criteria match rate fields, and how to resolve compound variables, as part of the primary selection criteria.
The two Rules in this section should be used together. The first Rule in Example 1 (NEWRULE5) shows how to set a variable as a result of an incoming event and then increases the value of the variable by 1.
The second Rule (NEWRULE6) shows how a Rule can fire when the variable value (set by NEWRULE5) has reached or increased past the set limit. First, Example 1 shows how to set a variable whose value increases with each occurrence of the incoming event.
Using the Rules
To properly use the two Rules created in these examples, NEWRULE5 should come before NEWRULE6 in the Rule Set. In other words, NEWRULE6 should follow immediately after NEWRULE5.
Set the automation strategy of the Rule Set to FIRST, which means that events are evaluated through the Rule Set and only the first Rule that matches with an event will be fired. Once the Rule fires, the event is handled and subsequent Rules are not compared against the event and, therefore, will not fire.
In this example, each time the IEF403I message matches NEWRULE5, the value of variable &!a.imfjtype.&imfjnum will increase by 1. When the value reaches 13, the NEWRULE6 will fire because the value of the &!a.imfjtype.&imfjnum has become greater than 12 and an ALERT will be issued.
The ALERT will call attention to the fact that a job has started more than 12 times, which might indicate that the job needs operator attention.
This section contains the following topics:
Related topic