DSM/SCM Event Management Programming Manual

SPI Programming Considerations for DSM/SCM
DSM/SCM Event Management Programming Manual—529844-003
3-6
Creating and Loading a Filter Table
Creating and Loading a Filter Table
You can use filter tables instead of or in conjunction with the standard compiled filters.
Because a compile step is not required, filter tables offer ease of maintenance and
improved efficiency. They are particularly useful when you need to filter events by
simple criteria such as event number and subsystem ID and when you need frequent
and fast online update of filter contents.
The table contains four columns: subsystem owner, subsystem ID, event number, and
pass value (optional). The subsystem ID can be a name or number. A subsystem
owner can have several subsystem IDs, and a subsystem ID can have multiple event
numbers. The pass value is the same as the compiled filter's pass value and is
returned to the consumer application.
Filter Table Format
A filter table is represented as an edit file. When loaded into a distributor, the table is
automatically converted to a filter object and saved as a disk file. Once the object file is
available, it can be loaded into a distributor.
The format of the edit file is:
?COMMENT
EMS FILTER TABLE
?EMPHASIS n
?USER m,n
?COMMENT
owner subsys event# passval
?PASS n
owner-name subsys-name n3
subsys-number n1..n2
or or
wildcard wildcard
where:
EMPHASIS n is a function that returns TRUE (n = 1) or FALSE (n = 0), depending
on whether the current event message is potentially critical.
USER m,n is the subsystem owner, m is the group, and n is the user ID.
PASS is a statement that selects or rejects the event message that the filter
is currently examining.
?COMMENT is information for your use.