TS/MP 2.5 Management Programming Manual

Event Messages and the ViewPoint Application
Event messages logged to $0 result in a textual display on the ViewPoint screen. Console messages
that are logged to $0 are normally also echoed to the ViewPoint application. To avoid duplication,
console messages logged to $0 are only included on the ViewPoint display when neither the LOG1
nor the LOG2 command specifies the EVENTFORMAT parameter.
Event Message Destinations
Event messages are sent to the files you specified in the PATHCOM LOG1 and LOG2 commands,
or in the ZLOG1INFO and ZLOG2INFO fields of ZPWY-MAP-PAR-CONTROL-PM token (sent in
the CONTROL PM command buffer). The Pathway subsystem does not report event messages to
the HP Tandem Maintenance and Diagnostic System (TMDS).
HP recommends that the collector process, $0, be specified for event logging. You can also use
a process or disk file as the destination for event messages. If you log events to a disk file, it is
simplest to use an entry-sequenced structured file and specify a record length that is at least equal
to the length of the longest event message. You can write a program to read event messages from
the file and use the EMSTEXT procedure to format them as display-format messages.
If you specify event reporting to an unstructured file, special processing is required when reading
the file. Your program must first extract the length of the current event message from the event by
calling the SSGETTKN procedure with the ZSPI-TKN-USEDLEN token to determine how to position
to the next event message. For odd unstructured files, event messages always begin on a word
boundary.
Console Printing
The Pathway subsystem does not use the ZEMS-TKN-CONSOLE-PRINT token. This means that event
messages are not processed by the compatibility distributor and, therefore, are not displayed on
consoles running versions earlier than C00. If Pathway subsystem messages must appear on the
console, configure the your subsystem to send messages to $0 in console format.
For example, this command prints text messages on the console:
LOG1 $0, STATUS
The console message is also routed to the ViewPoint application, unless the log specified with the
LOG2 command is configured with the EVENTFORMAT attribute.
Error Lists and Error Recovery
Pathway subsystem event messages do not contain error lists to describe errors reported by other
subsystems. These errors are indicated by simple tokens. For example, when the PATHMON process
reports a file system I/O error (such as ZPWY-ERR- PM-PATHCTLIO), the error value is reported in
the token ZPWY-TKN-ERROR.
If an error occurs while error or status information is being written to a log file, the PATHMON
process:
1. Closes the log file specified with the ZFILE option.
2. Opens $0 (a collector process provided with the Pathway subsystem).
3. Writes the information to $0. PATHMON process writes error information, status information,
or both to $0 depending on what was specified for the initial log file with the ZSTATUS field.
Additionally, PATHMON process writes the information to $0 in the same format (that is, event
messages or text) specified for the initial log file with the ZEVENTFORMAT field.
If an error then occurs while information is being written to $0, the PATHMON process closes $0
and prohibits further error and status logging. The PATHMON process does not reopen either the
log file or $0.
This example commands configure two log files:
Event Management Programming for Pathway Subsystems 165