EMS Manual

Generating Standard Events
EMS Manual—426909-005
10-26
Task 8.12: Compile Your DDL Definitions

DDL DEF. Specify the DDL definition that defines the fields of your extensible
structure token:

Name your definition as ss-DDL-structname.

Define all your DDL definitions in one place in the common DDL structure
definitions section.

SSID clause. See Defining a Simple Token.

HEADING clause. See Defining a Simple Token.

NOVERSION or VERSION clause. If version is specified, it must be greater than
the last version field used. The subsystem must define its value.
If you must use MAP tokens, for more information on how they work, see the SPI
Programming Manual.
Task 8.12: Compile Your DDL Definitions
Follow the established build procedure of your company.
Task 9. Create and Build Your EMS Templates
You must provide an EMS template file to display the events of your subsystem which,
at a minimum, describes the SSID, name, and version of your subsystem.
Each step corresponds to a section in the sample EMS template file.
If you provide the cause, effect, and recovery of an event in templates, do not define
those templates in this file. You should have already defined those templates in
another template file in Task 6. Design Your Event Messages on page 10-15.
1. Prepare the EMS template file sample file.
a. In the NonStop Technical Library, copy and paste the text under EMS
Templates Sample File on page C-30, into a .txt file in any text editor.
b. Transfer the .txt file to your subvolume.
c. Rename the .txt file in your subvolume to SsssTMPL (for example,
SSAMTMPL), where Ssss is the subsystem acronym, using an S at the
beginning. (ZsssTMPL is the template object.)
2. Provide a description (the SSID, SSNAME, and VERSION) of your subsystem.
3. If you defined your own enumerations with 89 enumeration clauses to any of these
standard EMS tokens:
ZEMS-TKN-CONTENT-USER ZEMS-TKN-CHANGE-REASON
ZEMS-TKN-STATE-CURRENT ZEMS-TKN-TXFAULT-TYPE
ZEMS-TKN-STATE-PREVIOUS ZEMS-TKN-UTIL-UNIT