DSM Template Services Manual

DSM Template Services Manual—427187-004
A-1
A Template-Related DDL Clauses
This section gives brief descriptions of a few DDL clauses. For detailed information,
see the Data Definition Language Reference Manual . If you are writing a new
application that uses Template Services in some way, this material might be especially
useful. If not, you might read it to help you understand DDL standard definition files.
When making changes in a DDL source file, to give DSM Template Services access to
the up-to-date information, you must also:
•
Remake DDL dictionaries.
•
Remake template files that depend on these dictionaries.
•
Install the resulting templates in your system.
SSID Clause
This DDL clause identifies the application associated with a token code or token map.
With SSID present, the Template Compiler copies the token information from the DDL
dictionary to a record in the correct template object file. Without SSID, the Template
Compiler (and thus DSM Template Services) loses access to token names and to the
information from the DDL clauses described here. In that case, the
SPI_BUFFER_FORMAT procedures can produce only a numbered list of token values.
HEADING Clause
This DDL clause gives DSM Template Services the information needed to label a token
or field value in the display text.
DISPLAY Clause
This DDL clause gives DSM Template Services the edit code to use when translating a
token or field value to display text. Include this clause if a DISPLAY format code might
make the value more readable or if the default is not suitable for this token or field.
TYPE ENUM Clause
Many integer tokens (or fields) contain code values with text-string equivalents: values
0, 1, and 2 for stopped, slow, and fast, for example. Consider defining such a token as
a DEFINITION statement TYPE ENUM clause and placing the text strings in AS
clauses. Then text strings that represent the integer values can be returned to
EMSTEXT and SPI_BUFFER_FORMATNEXT_ procedures.