DSM Template Services Manual

Template Language
DSM Template Services Manual—427187-004
3-3
Language Basics
PROGRAMFILE tokens. For information on value replacement and other edit-marker
operations, see Edit Markers on page 3-19.
For a description of the syntax of individual statements and their order in the source
file, see Statements on page 3-6.
Language Basics
This subsection explains general features of the Template Language.
Comments
These comments are ignored by the Template Compiler:
•
Two equal signs (==) and the characters that follow them on the same line
•
Characters enclosed in braces ({}) within a line
Comments can go anywhere in the source file.
Blank Space
To improve source-file readability, you can use extra spaces between language
elements and use blank lines anywhere.
Names
All names used in template source statements (of tokens, constants, subsystem IDs,
and so forth) are DDL names and must be defined in the DDL dictionary used when
the template source file is compiled. For details, see DICT Statement on page 3-7.
Within each name, use hyphens as in DDL and COBOL, rather than carets as in TAL
or TACL; for example, ZEMS-TKN-EVENTNUMBER.
Specifying a Token Name
To know whether to qualify a token name in the Template Language, you must
visualize the context of the token it is to match in the SPI buffer. For information on the
format of tokens in a SPI buffer, see the Distributed Systems Management (DSM)
Manual .
In a Template Language statement, you can use a normal (unqualified) token name in
these cases:
•
If the subsystem ID of the token in the SPI buffer and its default subsystem ID are
the same
•
If the token is a shared token (for example, certain ZEMS tokens and all ZSPI
tokens)