EMS Manual

EMS Manual—426909-005
20-1
20 Collector Event Messages
Primary and alternate collectors receive and log event messages sent to them by
subsystems. Collectors also generate event messages for their own log files. In
general, these event messages report events occurring in the collector environment.
The subsystem ID (ZSPI-TKN-SSID) for collector-generated messages is EMS (Event
Management Service). Each message has an event number that uniquely identifies it
within the group of EMS event messages.
This section describes event messages generated by EMS primary and alternate
collectors:
Types of Collector-Generated Messages
There are four types of collector-generated messages: tokenized operator-console
messages, tokenized text messages, primary collector event messages, and alternate
collector event messages.
Tokenized Operator-Console Messages
Numbered operator-console messages are written to the primary collector by privileged
routines. These privileged routines are internal to HP and are not in this manual. The
primary collector converts these messages to a tokenized form and gives them an
event number that is the same as the console-message number. The collector then
writes the messages to the primary collector log file.
Tokenized Text Messages
Subsystems can write text messages to a primary or alternate collector using the
WRITE procedure. The collector converts these messages to tokenized form, gives
them the event number 512, and writes them to that collector’s log file.
Primary Collector Event Messages
The primary collector generates event messages to describe occurrences in its
environment. These messages are then written to the primary collector log file. They
inform you of these kinds of events:
Topic Page
Types of Collector-Generated Messages
20-1
Summary of Collector-Generated Messages 20-2
Tokenized Operator Console Messages (1–511) 20-4
Tokenized Text Messages (512) 20-7
Collector-Specific Event Messages 20-9