EMS Manual

Compiled Filters
EMS Manual—426909-005
5-45
Compiler Directives
Before compiling a filter, you must load the standard definitions for SPI and for any
subsystem whose names you use in the filter. Loading standard definitions defines the
names for a subsystem: names of tokens, names of values, and most other names that
you might need.
Names of subsystem IDs are defined but not initialized by loading the standard
definition files. You can place TACL commands at the beginning of a filter (in brackets)
to initialize subsystem IDs.
This SET command initializes the subsystem ID for the TMF subsystem:
[#SET ZTMF^VAL^SSID
[ZSPI^VAL^TANDEM].[ZSPI^SSN^ZTMF].[ZTMF^VAL^VERSION] ]
All standard definition files reside in the $SYSTEM.ZSPIDEF subvolume or can be
placed on another volume at the choice of the operations staff at your site. For more
information on standard definition files, see the SPI Programming Manual.
You must load the standard definitions of SPI and of each subsystem whose tokens
you use. These TACL statements load the standard definitions for SPI and EMS:
#PUSH dummy
#LOAD /KEEP 1, LOADED dummy/ $SYSTEM.ZSPIDEF.ZSPITACL
#LOAD /KEEP 1, LOADED dummy/ $SYSTEM.ZSPIDEF.ZEMSTACL
#POP dummy
If your site places the standard-definition files on another volume, change $SYSTEM to
the other volume name in these statements.
For information on how to create and attach a TACL segment file, see the TACL
Reference Manual. It provides a quick way to save and restore standard definitions.
Loading standard definitions defines the names of tokens and many other definitions
that you need.
Compiler Directives
The compiler supports the LIST, NOLIST and SOURCE directives. Each directive must
begin with a question mark (?) in the first character position and must be on a line by
itself.
LIST Directive
The LIST directive causes current source statements to be included in the compiler
output file. For details, see also the NOLIST directive.
?LIST