EMS Manual

Generating Standard Events
EMS Manual—426909-005
10-18
Task 7.3: List the Standard Management Functions
Your Subsystem Supports

Whether your subsystem interacts with processes from another subsystem either
in the generation of your events or in the management of your subsystem. If so,
describe these processes.

Whether your subsystem depends on tokens and events defined by another
subsystem. If so, briefly describe the subsystems and EMS files that you need (for
example, ZSPIDDL, ZEMSDDL, and ZCOMDDL).

Describe the command and control interface a user can use to inquire about or
control an object reported in your events, and where to find more details.

Whether your subsystem has a manager process. If so, whether it is reported in an
event. Provide this information about the manager:

Its function, and whether it resolves object names or is the focal point for
commands to control and inquire about an object.

What kind of process it is (a process pair, a persistent process, or neither),
whether you can have more than one manager process and, if so, what the
implications are.

Its name. Whether it is a well-known (fixed) name or if it changes depending on
the event.

Whether you are generating events for EMS only or if you are also generating
events for TMDS or TSM.

Whether you send events to the primary collector or to an alternate collector.
If possible, your subsystem should let the destination collector be configurable for
better flexibility.
Task 7.3: List the Standard Management Functions Your
Subsystem Supports
Standard Event Types You Can Generate Corresponding Standard Management
Functions to Check in Your ES
Object Available Object state monitoring
Object Unavailable Reactive problem management
Object Other State Change Object state monitoring
Transient Fault Proactive problem management
Usage Threshold Proactive problem management
Operator Attention Needed Production requests requiring operator
Operator Attention Completed Production requests requiring operator