EMS Manual

Compiled Filters
EMS Manual—426909-005
5-12
Tokens
Example 2
This example shows an indexed token reference:
ABC^TKN^STUFF(3) = 5
In this example, the value of a stuff token is compared to 5.
Specifically, the event message is searched, from left to right, until the third stuff
token is found. The value of that token is then compared with 5.
If the event message contains fewer than three stuff tokens, the value of the
comparison is FALSE. For details, see Comparisons With Missing Values on
page 5-25.
EMF Default Subsystem ID
If you refer to a token without qualifying the token name by a subsystem ID, the token
owner is provided by the EMF (EMS filter) default subsystem ID. By using this default,
you can avoid explicit token qualification in most cases. The default subsystem ID is
defined everywhere within the filter specification. Unless you change it, the EMF
default is the NULL subsystem ID. To change the EMF default subsystem ID, use a
compound statement. For details, see Compound Statement on page 5-31.
NULL Subsystem ID
When you specify a NULL subsystem ID, the filter supplies the value of the
ZSPI^TKN^SSID token in the event message it is currently examining.
ZSPI^TKN^SSID identifies the subsystem that reported the event. Therefore, if the
filter is examining a Pathway or HP NonStop Transaction Management Facility (TMF)
event message, the NULL subsystem ID represents Pathway or TMF, respectively.
Within EMF, 0.0.0 designates the NULL subsystem ID.
Qualified Tokens
To refer to tokens by names that are qualified by subsystem IDs, use this syntax:
ssid
is the subsystem ID that specifies the token owner. (Include ZEMS^VAL^SSID or
TANDEM.EMS.0 to represent the EMS subsystem, for example.)
token-name
is the token name.
SSID ( ssid , token-name [ ( index ) ] )