EMS Manual

Generating Standard Events
EMS Manual—426909-005
10-6
Task 2.5: Design Your Asynchronous Management
Interface

If a command and control interface does not exist for the object reported in your
events, why generate the event?

If no action can be taken on the object by a user or program, directly or indirectly,
why generate the event?
Task 2.5: Design Your Asynchronous Management Interface
Define the asynchronous management interfaces for objects that need to record or
report their changes immediately, like state changes, as a result of encountering
certain situations in the system.
Task 2.6: Design Your Command and Control Management
Interfaces
Command and control management interfaces let:

You configure, control, or inquire about your objects

Operators and management applications change how your subsystem operates
They are integral to the manageability of your subsystem and must be provided. They
include command interpreters for operators (for example, SCF, TMFCOM, PATHCOM)
and programmatic interfaces for management applications (for example, SPI).
Task 3. Generate Standard Events for Your
Subsystem
Determine the standard events and the event subjects for events that your subsystem
should generate, and customize these standard events to your environment.
Task 3.1: Determine the Operational States of Your Objects and
Subsystem Functions
1. Generate an event for states that you can detect (as defined in Object State
Monitoring Functions on page 9-4):
Type of Information Asynchornous Management Interface
EMS, TMDS or TSM Object state change information
MEASURE Performance and workload data
Audit services Security data
Operational State Event Type to Generate (page1of2)
Unavailable Object Unavailable