EMS Manual

Generating Standard Events
EMS Manual—426909-005
10-13
Task 4.4: Specify the EMS Event Types for Your
System Data
Data for Problem Resolution
To foster problem resolution, provide:

Recommended action—the subsystem's best guess at how to correct the problem.
This sometimes fixes the problem, but not always. It is difficult for a subsystem to
determine the correct recovery action without having all the problem information.

Manager process name—for the failed object. If there is no manager process, it is
the name of the process that provides the command and control interface to
control the failed object.
Data for Problem Tracking and Control
To foster problem tracking and control, provide:

Version of the subsystem that contains the problem

A unique character string identifying the place in the subsystem code that had the
problem
Task 4.4: Specify the EMS Event Types for Your System Data
The system data items you have identified are the tokens in an EMS event.

If several conditions are reported using a single EMS event, consider defining
multiple EMS events with each event reporting only one significant condition. The
resulting events are more meaningful. For example, Section 9, Standard Events,
defines an Object Available, Object Unavailable, and Other State Change events
instead of one general event to report object state changes.

Define enumerated values (if they do not already exist) for these event types. One
of these values will be stored in the ZEMS-TKN-CONTENT-USER token.
Task 5. Migrate Existing Events
If your subsystem currently generates nonstandard events, read Migration Rules and
then do one of:

Incorporating Old Events Into New Events on page 10-14

Revising Old Events on page 10-14
If you do not have existing nonstandard events to migrate, continue with Task 6.
Design Your Event Messages on page 10-15.
Migration Rules
Do not change an EMS event if the changes will force existing management
applications to change.
You cannot: