EMS Manual

Generating Standard Events
EMS Manual—426909-005
10-20
Task 7.8: Enumerate Your Private Values to
Standard EMS Tokens
Task 7.8: Enumerate Your Private Values to Standard EMS
Tokens
If you have private values for these tokens, define their values ss-VAL-valuename
and list them under the token in your ES:
ZEMS-TKN-CHANGE-REASON
ZEMS-TKN-CONTENT-USER
ZEMS-TKN-STATE-CURRENT
ZEMS-TKN-STATE-PREVIOUS
ZEMS-TKN-TXFAULT-TYPE
ZEMS-TKN-UTIL-UNIT
Task 7.9: List Private Tokens From Other Subsystems
If you use tokens defined by other subsystems—other than SPI or EMS—create a new
subsection {4.3.x} for each subsystem and list their tokens there. List these tokens
under the headings “Common ... tokens” or “Event-specific ... tokens.”
Task 7.10: List Private Tokens From Your Subsystem
If you specify private tokens, list them in your ES with this explanation:

Name of the token—for example, ZSAM-TKN-tokenname

Type of token—for example, ZSPI-TYP-STRING

Kind of token—conditional (C) or unconditional (U)

List of possible values with brief description

If conditional, under what conditions the token is provided and what the default
meaning is if the token is not provided
Task 7.11: Describe the Details of Each Event Message
1. Create a new subsection {5.x} in your ES to describe each of your event
messages. Order the subsections alphabetically by the symbolic event names.
2. Describe your event messages by using one of the templates provided in the ES:

Unconditional tokens, conditional tokens, internal tokens
a. List the private tokens you defined.
b. List the standard tokens only if the token contains more specific values
than those defined for the token in ES {3.0} or if you want to provide your
own event-message text and you need to reference that token in your
description.

Event message text