TMF Management Programming Manual (H06.06+, J06.03+)
Table Of Contents
- HP NonStop TMF Management Programming Manual
- Legal Notices
- Contents
- What’s New in This Manual
- About This Manual
- 1 Introduction to TMF
- 2 Communicating With the TMFSERVE Process
- 3 SPI Programming Considerations for TMF
- 4 Common Definitions
- 5 Commands and Responses
- Command Summary
- Command Descriptions
- ABORT TRANSACTION
- ADD AUDITTRAIL
- ADD DATAVOLS
- ADD DUMPS
- ADD MEDIA
- ADD RESOURCEMANAGER
- ALTER AUDITDUMP
- ALTER AUDITTRAIL
- ALTER BEGINTRANS
- ALTER CATALOG
- ALTER DATAVOLS
- ALTER DUMPS
- ALTER MEDIA
- ALTER PROCESS
- ALTER TMF
- CANCEL OPERATION
- CLOSE RESOURCEMANAGER
- DELETE CATALOG
- DELETE DATAVOLS
- DELETE DUMPS
- DELETE MEDIA
- DELETE RESOURCEMANAGER
- DELETE TMF
- DELETE TRANSACTION
- DISABLE AUDITDUMP
- DISABLE BEGINTRANS
- DISABLE DATAVOLS
- DUMP FILES
- ENABLE AUDITDUMP
- ENABLE BEGINTRANS
- ENABLE DATAVOLS
- INFO ATDUMPDM
- INFO ATVOLUME
- INFO AUDITDUMP
- INFO AUDITTRAIL
- INFO BEGINTRANS
- INFO CATALOG
- INFO DATAVOLS
- INFO DUMPS
- INFO MEDIA
- INFO PROCESS
- INFO RESOURCEMANAGER
- INFO TMF
- LIST AUDITTRAIL
- NEXT AUDITTRAIL
- RECOVER FILES
- RELOCATE DISKDUMPS
- RESOLVE TRANSACTION
- START TMF
- STATUS ATFILE
- STATUS AUDITDUMP
- STATUS AUDITTRAIL
- STATUS BEGINTRANS
- STATUS CATALOG
- STATUS DATAVOLS
- STATUS OPERATION
- STATUS RESOURCEMANAGER
- STATUS RMTRANSBRANCHES
- STATUS TMF
- STATUS TMFSERVER
- STATUS TRANSACTION
- STATUS TRANSACTIONCHILDREN
- STOP TMF
- 6 Event Messages
- 7 Error and Warning Messages
- A TMF Configuration Limits and Defaults
- Index

SPI Programming Considerations for TMF
HP NonStop TMF Management Programming Manual—540140-010
3-8
Security
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.
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 Section 5, Commands and
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 Event-
Management Considerations for TMF on page 3-9.)
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
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.










