OSI/MHS Management Programming Manual

Introduction to Management Programming for
OSI/MHS
OSI/MHS Management Programming Manual—424824-001
1-8
Event-Management Interface
Event-Management Interface
Event and accounting messages from OSI/MHS are made available to management
applications by the Event Management Service (EMS). EMS collects, logs, and
distributes event messages that provide information to help you monitor the OSI/MHS
subsystem, analyze failures, and recognize and handle critical problems. EMS does the
following:
•
Provides different descriptions of events for human beings and for programs, so that
each has the information available in the form best suited to its needs
•
Lets the operator or application retrieve only those messages relevant to the task at
hand
•
Allows flexible distribution of event messages within a system or network
EMS has token-oriented programmatic interfaces for both event reporting and event
retrieval. It includes special high-level procedures, based on SPI procedures, to format
information about an event as a special type of SPI message (called an event message)
and to retrieve information from event messages. An event message includes tokens
that identify the subsystem that reported it, the system component that is the subject of
the event, the particular kind of event that occurred, and other information about the
event.
For OSI/MHS, EMS also collects accounting messages. The system events (event
messages) are collected in primary collectors; the accounting messages are collected in
alternate collectors.
Figure 1-5
shows an overview of the OSI/MHS event management interface.
Note. When the terms event and token appear in this manual, they refer to DSM events and
tokens, as defined in the SPI Programming Manual and the other DSM manuals.