|
|
|
If the message text passes the filtering process, further validation is performed to see whether the message received meets the specified execution conditions.
All the execution conditions specified on the Message Filter panel must be met before the message rule can be triggered. The following shows an example.
. Execution Conditions -------------------------------------------------------. | | | Job Name .... Rule Priority ........... (1 is best) | | Job Type .... Execute If Not Best Fit? | | | | Mon Tue Wed Thu Fri Sat Sun Time Start End | | On Days NO NO YES NO NO NO NO Range1 ... | | Range2 ... | | | ’-----------------------------------------------------------------------------’
Important! If you want to detect a message from a started task that runs under the master scheduler (that is, by using the SUB=MSTR operand), do not use the Job Name and Job Type fields.
You need to take into consideration that there may be more than one rule that applies to the same message.
EventView selects and executes the rule considered to be the best fit. This decision is based on how specific the filtering and execution conditions are; the more specific the rule (for example, the more message text specified), the better the fit.
You can override this determination of the best fit by entering a value (in the range 1 to 99) in the Rule Priority field, to indicate the order of importance. Top priority rules are given a ranking of 1, while the least important rule can be ranked 99.
You may want to trigger multiple rules for one message. The Execute if Not Best Fit? field, which can be set to Yes or to No, functions as follows:
| Copyright © 2010 CA. All rights reserved. |
|