TS/MP 2.5 Management Programming Manual

LOG1 $0, EVENTFORMAT
LOG2 $DATA.PM.LOGFILE, STATUS
If an error occurs on LOG1, the PATHMON process closes the log because the error occurred on
$0; PATHMON process does not reopen LOG1. If an error occurs on LOG2, the PATHMON
process reopens $DATA.PM.LOGFILE as LOG2 $0, STATUS. The PATHMON process then sends
both error information and status information to $0 because LOG1 used the default value
(ZPWY-VAL-OFF) for ZSTATUS and LOG2 specified ZPWY-VAL-ON for ZSTATUS. Additionally,
the PATHMON process sends both event messages and text messages to $0 because LOG1
specified ZPWY-VAL-ON for ZEVENTFORMAT and LOG2 used the default value (ZPWY-VAL-OFF)
for ZEVENTFORMAT.
Message Filters
EMS provides you with the capability to create programs called filters, which allow applications
to select particular event messages from among all the event messages that are issued. Filters select
event messages to be returned to an application by examining the values of tokens in the event
message.
Any of the tokens in an event message can be used for selecting the event messages to be returned
to an application. You can create filters that return all event messages issued during a particular
time period, all event messages with a certain event number, all event messages associated with
a particular CPU, and so forth.
When designing event-message filters, consider the following:
• 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 to 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 allocates 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.
166 Event Management