EMS Manual
Generating Standard Events
EMS Manual—426909-005
10-3
Task 2.1: Identify Types of Objects to Manage in
Your Subsystem
Provide automated recovery for your functions whenever possible. When you cannot,
provide specific information about:
The problem so that management applications can be written to quickly recover
from failures
Potential problems so that actions can be taken to prevent severe degradation in
your subsystem service
Section 9, Standard Events, standardizes the information—EMS events and tokens—
and the conditions under which to report this information to management applications.
Thoroughly analyze your subsystem and its environment to determine the objects that
should report these events and their error and diagnostic information. The more
thorough your analysis, the more manageable your subsystem will be.
Task 2.1: Identify Types of Objects to Manage in Your Subsystem
1. Identify all objects that your subsystem controls, provides, or uses:
A hardware component (ATM machine, CPU, disk, controller, bus, channel, or
modem) that your subsystem controls
A software component (process, file, transaction, database, or piece of
microcode) that your subsystem controls or uses
A service (cash withdrawal function in an ATM, or reliable transport service)
that your subsystem or application provides
A resource (tape, disk, or buffer pool) that your subsystem uses
2. Determine which objects to manage:
Think about the people and programs that will use your subsystem.
Think in terms of the services and the service level objectives—such as
availability and performance—that your subsystem provides.
Objects needed by operators and management applications to help your
subsystem maintain these service levels when one or more of your functions
become unavailable (planned or unplanned) or when performance degrades.
3. Do not overlook:
Functions performed by your subsystem, especially those externalized by your
programmatic or interactive user interfaces
Functions performed or provided by any utilities your subsystem provides
Services and resources your subsystem uses (Often overlooked when
designing the management interface, they might be critical to the operation of
your subsystem.)