Buffer Size; Descriptions Of Event Messages; Console Printing; Subsystem Id - HP NonStop TMF Programming Manual

Event Messages
position itself to the next event message. Your program must do this by calling the
SSGETTKN procedure with the ZSPI-TKN-USEDLEN token. Event messages always
begin on a word boundary for odd unstructured files.
Note. Information in TMF event messages is encoded in individual tokens; TMF event
messages do not use structured tokens.

Console Printing

TMF uses the CONSOLE-PRINT token (ZEMS-TKN-CONSOLE-PRINT), which
recommends that the event message be processed by the compatibility distributor. For
more information about this token, see the EMS Manual.

Subsystem ID

The subsystem ID in each TMF event messages is ZTMF-VAL-SSID.

Action Events

TMF does generate action events.

Buffer Size

Your program should allocate at least 512 bytes for retrieving TMF event messages.
512 bytes is the minimum buffer size.
Event Filtering
You can design event-message filters based on specific tokens, token values, or
ranges of token values:

The SSID token (ZSPI-TKN-SSID) distinguishes events that are reported by TMF.

The event number token (ZEMS-TKN-EVENTNUMBER) distinguishes event
messages reported by the TMP, TMF monitor process (TMFMON), volume
recovery processes, file recovery processes, and backout processes.

Descriptions of Event Messages

The following pages describe each event message that can be issued by TMF. The
descriptions appear in ascending order by event number; that is, in ascending order by
the ZTMF-EVT- values.
Each description includes a syntax box showing the tokens that TMF can place in the
message buffer in addition to the common tokens described in this section under
Common Tokens in Event Messages
not present in all TMF event messages or if their values differ from one event message
to another.
HP NonStop TMF Management Programming Manual—540140-008
on page 6-1. Tokens appear in the box if they are
6-19
Console Printing