DSM Template Services Manual

Template Language
DSM Template Services Manual427187-004
3-13
DEF_ENUM Statement
For the corresponding DDL definition files, see Example 3-6 for the FEET subsystem
and Example 3-7 for the LEGS subsystem.
Example 3-5. DEF_ENUM Example—Template Source File
== TEMPLATE COMPILER SOURCE
== \cat.$kit.clstacl.t5
VERSION: "LEGS subsystem with DEF_ENUM statements 91/06/21"
DICT: \cat.$kit.clstacl
SSID: legs-val-ssid
SSNAME: "LEGS", "LEG"
== This SHARED_SSID statement specifies that LEGS uses the
== definitions in the DDL definition file of FEET.
SHARED_SSID: feet-val-ssid
== DO_COMMON N.A.
== FORMAT N.A.
== Associate the shared token feet-tkn-retcode with the enumerations
== feet-ddl-retcode-state and legs-ddl-domain-state. For the definitions
== of the shared token and the enumerations, see the DDL definition files
== for the FEET and LEGS subsystems.
DEF_ENUM: feet-tkn-retcode AS feet-ddl-retcode-state, legs-ddl-domain-state
== If the token zems-tkn-eventnumber has the value legs-evt-print-retcode,
== then use the following message text. If the token feet-tkn-retcode has a
== value matching one of the enumerated values of feet-ddl-retcode-state or
== legs-ddl-domain-state, then the corresponding text is placed where
== the edit marker <1> is placed in the message text. If there is no matching
== value, then UNDEFINED is printed.
MSG: zems-tkn-eventnumber, legs-evt-print-retcode
"domain state is <1>"
1: feet-tkn-retcode