TMF Management Programming Manual (G06.24+)

Event Messages

HP NonStop TMF Management Programming Manual—522420-002

6-17

Event-Management Programming for TMF

Each TMF event is reported to the EMS collector process ($0) and displayed in text on

the ViewPoint console. Although the EMS collector process ($0) is the recommended

method for logging event messages, you can also use a process or disk file to log

them.

The easiest method of logging events to a disk file is to use an entry-sequenced,

structured file, and specify a record length longer than or equal to the longest event

message. You can write a TACL routine that uses the #EMSTEXT and #EMSTEXTV

built-in functions to read event messages from the file, and then format them as text

messages.

You can specify an unstructured file to log event messages, but any program that

reads it must first extract the length of the current event message to determine how to

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.

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.

Note. TMF event messages are not reported to TMDS, and they cannot be logged to a

terminal, a printer, or an operator process (on a pre-C00 version of the NonStop Kernel).

Note. Information in TMF event messages is encoded in individual tokens; TMF event

messages do not use structured tokens.