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
Commands and Responses
HP NonStop TMF Management Programming Manual—540140-010
5-200
STATUS TRANSACTION
ZTMF-VAL-Aborted
specifies transactions that have been aborted. A transaction enters this
state when all of its effects are undone and the ABORTTRANSACTION
record is written to the audit trail. A transaction normally stays in this state
only briefly. But, in the case of a distributed transaction on a remote node,
if the remote node (the child node, in this case) unilaterally aborts a
transaction, that transaction remains in the aborted state until the parent
node is informed of the outcome.
ZTMF-VAL-Committed
specifies transactions in the committed state. A transaction enters this
state when the ENDTRANSACTION record is written to the audit trail. A
transaction normally stays in this state only briefly. However, in a
distributed transaction, a parent node cannot remove a committed
transaction until all child nodes have been informed of the commitment.
ZTMF-VAL-Prepared
specifies distributed transactions in the prepared state. A distributed
transaction enters this state on a remote node after Phase 1 of the
commitment is complete on that node; the transaction remains in this state
until the remote node is informed by its parent of the transaction’s
outcome.
ZTMF-VAL-Hung
specifies transactions hung during backout. A transaction enters this state
if the backout process attempts, but fails, to abort it.
If you omit this token, the default is all states.
ZTMF-VAL-Ending
specifies transactions in ending state. A transaction enters this state when
it is waiting for locks to be released. A transaction normally stays in this
final state for a very short time.
If you omit this token, the default is all states.
ZStatusDetail
specifies the level of detail to be returned. The following values are valid:
ZTMF-VAL-Status-Detailed
Detailed information is returned.










