TS/MP Management Programming Manual (G06.24+, H06.03+)

Event Management
NonStop TS/MP Management Programming Manual—540082-001
10-2
Event Management Programming for Pathway
Subsystems
For TS/MP, the PATHMON process logs event messages for itself and for LINKMON
processes. For Pathway/iTS, the PATHMON process logs event messages for itself
and for the TCPs.
You configure event logging using either the PATHCOM LOG1 and LOG2 commands
or the programmatic CONTROL PM command. Your management application can
specify the file to which PATHMON process logs events; whether PATHMON process
opens a specified log file; whether PATHMON process logs status change messages
as well as error messages; and whether messages are formatted as text or as event
messages.
A Pathway subsystem event message might express, among other conditions:
•
A change in the state of an object. For example, a server has started.
•
The failure or absence of a component. For example, a backup process has failed.
•
A file system error. For example, an error has occurred on a call to a file system
procedure.
•
The encountering of an invalid item. For example, a program-unit name is invalid.
Event Management Programming for Pathway
Subsystems
To process an event message, a management application must:
1. Start a copy of the EMS event distributor (EMSDIST).
2. Issue appropriate distributor programmatic commands, selecting the collector or
log file from which the events are to be retrieved and specifying the filter to be used
in selecting the events.
3. Issue a GETEVENT command to the EMS event distributor.
4. Use the EMSGET procedure to extract the event message from the response
buffer.
5. Use the EMSGET procedure to extract individual tokens from the event message.
6. Perform whatever actions are necessary to handle the event.
You can find general information about managing events as part of Distributed
Systems Management in the EMS Manual.
Event management information specific to the Pathway subsystem are.