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

Event Management

NonStop TS/MP Management Programming Manual—540082-001

10-3

Console Messages versus Event Messages

The PATHMON process generates error and status messages as console messages

and event messages. The event messages produce display-format messages when

operated on by the EMSTEXT procedure. Console messages and display-format

messages are logically similar, but not identical to each other.

Event-message numbers are the same as the numbers of the corresponding console

messages. For example, status message 1005 (SHUTDOWN) has the same number

as event message 1005 (ZPWY-EVT-PM-SHUTDOWN).

An event-message definition can be extended in any new version of TS/MP to include

additional tokens. Any token that is not identified as an unconditional token can be

deleted from an event-message definition.

Formatting Messages

In the interactive PATHCOM interface, the EVENTFORMAT attribute in the LOG1 and

LOG2 commands specifies whether the PATHMON process should format messages

as text or as event messages. Omitting EVENTFORMAT indicates that PATHMON

process should generate console messages; including EVENTFORMAT indicates that

PATHMON process should generate event messages.

For example, these commands specify that all error, status, and warning messages are

to be logged to $0 as both event messages and console messages:

LOG1 $0, STATUS

LOG2 $0, STATUS, EVENTFORMAT

To control event-message generation through the Pathway subsystem management

programming interface, use the CONTROL PM command, assigning the value ZPWY-

VAL-OFF or ZPWY-VAL-ON to the ZEVENTFORMAT field in ZPWY-DDL-PAR-

CONTROL-PM.

For the complete syntax of the PATHCOM LOG1 and LOG2 commands, see the

TS/MP System Management Manual. For the complete syntax of the Pathway

subsystem programmatic CONTROL PM command, see Section 8, Pathway

Subsystem Control Commands.

When the PATHMON process is first started, an initial log file is opened for messages,

as if you had issued the PATHCOM command LOG1 file-name, STATUS. This

initial file logs messages until you specify a LOG1 command to indicate otherwise.

Note. Message text can change from version to version. Your management application should

not depend upon the text generated by the EMSTEXT procedure.