Comparison operators
In filter and rule list parameters, the following operators are valid comparison operators.
Less-than (<), less-than-or-equal-to (<= or =<), greater-than (>) and greater-than-or equal-to (>= or =>) can be used for all INC/EXC parameters that have values other than Y|N.
Operator | Description |
|---|---|
= (equal) | Value of the parameter at run time must equal the specified value |
< (less than) | Value of the parameter at run time must be less than the specified value |
> (greater than) | Value of the parameter at run time must be greater than the specified value |
¬= (not equal to) | Value of the parameter at run time must be a value other than the specified value (the logical NOT symbol preceding the equal symbol is EBCDIC X'5F') |
=< or <= (less than or equal to) | Value of the parameter at run time must be less than or equal to the specified value |
=> or >= (greater than or equal to) | Value of the parameter at run time must be greater than or equal to the specified value |
The not-equal (¬=) operator is not supported with multiple values that are supplied to a MainView SRM parameter within parentheses The following examples demonstrate how to code multiple values without using the not-equal operator.
In the following example, the rule would trigger only when HSM_RC equaled 53 and HSM_ACTION equaled SPCMGMT or EXPIRED. This rule is a proper rule, because the HSM_ACTION variable is looking to match any one of the supplied values in the list.
If you want to change the rule to trigger only when HSM_RC=53 and HSM_ACTION was not equal SPCMGMT and EXPIRED, you should not supply multiple values to the HSM_ACTION parameter.
In this example, the rule would always trigger when HSM_RC=53. This is because HSM_ACTION will always be not equal to one of the values.
- If HSM_ACTION variable is SPCMGMT, it is also not equal (¬=) EXPIRED.
- If HSM_ACTION variable is EXPIRED, it is also not equal (¬=) SPCMGMT.
- If HSM_ACTION variable is anything else, it is also not equal (¬=) SPCMGMT.
There are a few ways to correctly write MainView SRM rules so they will trigger only when HSM_RC=53 and HSM_ACTION is not equal SPACMGMT and EXPIRED.
In this example, multiple values with a positive operand (=) on the first EXCLUDE (EXC) statement will bypass the previous SET statement when HSM_ACTION=SPCMGMT or HSM_ACTION=EXPIRED.
The INCLUDE statement that follows the exclude statement will trigger only when HSM_RC=53. This method is preferred to writing the rule, because it limits the statements to one SET statement.
Another alternative to writing the rules is to use two different SET statements with include (INC) statements.
In this example, multiple values with a positive operand (=) on the first SET statement will trigger when HSM_ACTION equals SPCMGMT or EXPIRED. However, the function is being set inactive every time HSM_ACTION is equal SPCMGMT or EXPIRED and no further rules are read for the function. For this reason, the previous example is generally recommended.
Less-than-or-equal-to (=< and <=) and greater-than-or-equal-to (=> and >=) symbols can be used for all INC/EXC parameters except those that have values of Y | N | YES | NO.