EMS Manual

Generating Standard Events
EMS Manual—426909-005
10-16
Task 6. Design Your Event Messages
For guidelines for the ZEMS-TKN-SUPPRESS-DISPLAY token, see Common-
Standard Tokens That Subsystems Provide on page 9-20.
4. Determine whether the manager process is relevant to the event. It is relevant only
if your event contains the ZEMS-TKN-NAME-MANAGER token.
5. Define whether the event is standard or private:

A standard event is an event defined in Section 9, Standard Events. It must
have a non-null ZEMS-TKN-CONTENT-STANDARD token value.

A private event is an event defined by you or another subsystem that is not a
standard event. The ZEMS-TKN-CONTENT-STANDARD token must have a
null value, and ZEMS-TKN-CONTENT-USER must have a non-null value.
6. Define unconditional and conditional tokens in the event:

Unconditional tokens are always present in an event (for example, the ZEMS-
TKN-EVENTNUMBER token).

Conditional tokens are present only under appropriate conditions. There is a
specific meaning if a conditional token is not present in the event. For example,
ZEMS-TKN-BATCHJOB-ID is a conditional token. Its absence means no job ID
is associated with the object.
7. Define whether the event has internal (volatile) tokens.
You can change internal tokens in an event message without notice. They are used
only by the subsystem.
8. Define the event message text to display for the event.
You must have an EMS template for your event. The template tells the EMSTEXT
program how to display your event message in operator console products like Web
ViewPoint. EMSTEXT uses the template you provided for an event before using
the standard template that EMS provides for each standard event.

For a standard event, use the standard template display. Do not provide a
different display unless:

The event has more than one subject.

The subject is not a printable ASCII string.

The event has private tokens that you think operators should see.

For a private (nonstandard) event, describe how to display the event.
The display of all event messages should look similar. Follow the standard
template format in Task 9. Create and Build Your EMS Templates
on page 10-26.
9. Define cause, effect, and recovery procedures for the event. Describe:

What causes the event to be generated

The effect the reported condition has on your subsystem, system, and network