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

Event Management
NonStop TS/MP Management Programming Manual—540082-001
10-6
Additional Programming Considerations
•
The Pathway subsystem that generated the event message is uniquely identified
by the name of the PATHMON process. The token ZSPI-TKN-MANAGER contains
this identification.
•
Event messages are classified as error, status, or warning messages by using the
token ZPWY-TKN-EVENTCLASS.
•
The token ZEMS-TKN-EVENTNUMBER distinguishes PATHMON process event
messages from link manager event messages. PATHMON process-initiated events
have values ranging from 1000 to 1999. Link manager-initiated event messages
have event numbers ranging from 3000 through 3999.
•
The token ZEMS-TKN-SUBJECT-MARK indirectly indicates the subject of the
event; for example, ZEMS-TKN-SUBJECT-MARK might appear with
ZPWY-TKN-SCNAME, indicating that a server process is the subject of the event.
Additional Programming Considerations
This information is specific to Pathway subsystems:
•
Buffer size—your program should allocate at least 2000 bytes for retrieving
Pathway subsystem event messages.
•
Variable-length records—event messages are variable-length records, which are
always written in a single WRITE operation with no folding or padding.
•
Event numbers—an event number identifies a particular event from a subsystem.
The Pathway subsystem has its own set of event numbers, which are 16-bit
integers represented in DDL by constants and in programs by TAL literals, COBOL
level-01 variables, or TACL text variables.
The event numbers have a one-to-one correspondence with a subset of the
existing PATHMON error numbers. The numbers are represented by symbolic
names of the form ZPWY-EVT-name, where name identifies the event.
•
Action events—the Pathway subsystem does not generate action events.
Event Messages
Each Pathway subsystem event message is contained within an event-message buffer
consisting of:
•
Message header token—contains the value ZSPI-VAL-EVTHDR, which identifies a
message as an event message. The event-message header is built by the
EMSINIT procedure. The header differs from the standard command header by
omitting some command and response tokens and including some standard EMS
tokens. Header tokens can be extracted from the event-message header by calling
the EMSGET procedure with specific token codes.
•
Standard EMS tokens—appear in all event messages.
•
Standard SPI tokens—appear in all event messages.