Security; Retrieving And Decoding Event Messages; Table 3-1. File-System Errors Returned By Tmfserve - HP NonStop TMF Programming Manual

SPI Programming Considerations for TMF
The TMFSERVE process does not provide support for continuing—despite errors—
through the use of the SPI standard token ZSPI-TKN-ALLOW-TYPE. The SPI standard
token ZSPI-TKN-RETCODE contains a nonzero value if the TMFSERVE process
detects an error in a command message—or in attempting to perform a command.
TMF can also return file-system errors. These errors are listed in

Table 3-1. File-System Errors Returned by TMFSERVE

Error
Number Description
11 A process name qualifier other than #ZSPI was used.
12 Too many requesters are attempting to communicate with TMFSERVE.
17 An OPEN request was received from a backup process, but the parameters do
not match those used to request the OPEN for the primary process; or
TMFSERVE was not opened by the primary process.
28 An attempt was made to open TMFSERVE with a NOWAIT depth greater
than 1.
39 The request has a sync ID that is older than the set of saved replies.
60 TMFSERVE has failed and has been replaced by a different process having the
same name since TMFSERVE was opened.
Note. Errors 39 and 60 can be returned in response to any command. The other errors are
returned only in response to a call to the OPEN procedure.

Security

TMF commands are either sensitive or nonsensitive. Sensitive commands can change
the state or configuration of subsystem objects; nonsensitive commands cannot. The
TMFSERVE process allows sensitive commands to be issued only by members of the
super group. The description of each command in
Responses identifies which users can issue the command.

Retrieving and Decoding Event Messages

The following is a summary of the steps your application must take to retrieve and act
upon event messages:
1. Declare a buffer of appropriate size for the Event Management Service (EMS)
GETEVENT command and its response. (For recommended sizes, see
Management Considerations for TMF
2. Start an EMS consumer distributor and open it using the #ZSPI qualifier.
3. Format an EMS distributor CONTROL programmatic command to load a filter you
have written, and to specify the source and destination of event messages, if
desired. Send the CONTROL command to the consumer distributor using the
HP NonStop TMF Management Programming Manual—540140-008
Section 5, Commands and
on page 3-9.)
3-8
Security
Table 3-1.
Event-