EMS Manual

Compiled Filters
EMS Manual426909-005
5-16
Constants
Integers
You can use any signed integer constant that can be expressed internally in 64 bits.
For example:
1 99 -523 32769 2114678910123456708
You write unsigned, integer constants the way you write signed, positive integers.
Strings
Surround the characters of a string constant with double quotes. For example:
"pqrstuvw"
Subsystem IDs
You can refer to a subsystem ID in either of two ways. First, you can use the name of a
TACL variable that has been appropriately initialized. For example, ZEMS^VAL^SSID
is the name of the subsystem ID for EMS. For information about how to initialize such a
subsystem ID, see The Filter Compiler on page 5-44.
Alternatively, you can represent a subsystem ID as a series of component parts:
organization
is the name of the organization associated with the subsystem. It includes from
one to eight letters, numbers, or dashes, beginning with a letter (HP, for example).
subsystem
is either an integer or a name. Each organization uses integers to represent its
subsystems; you can use an integer to specify subsystem. For subsystems for
the NonStop server, for example, you can use names such as the following to
specify subsystem.: EMS, DNS, TMF, EXPAND, FOX, MONITOR, and PATHWAY.
You can use org.name for any subsystem that is present in the system template
file. For a complete list of NonStop Kernel subsystem names and numbers, see the
Operator Messages Manual.
version
is either an integer or a version identifier. An integer represents the subsystem
version. This form is defined for all subsystems. A version identifier, such as D20,
represents the version of a NonStop Kernel subsystem. This form is defined only
for subsystems.
organization . subsystem . version