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-6
ABORT TRANSACTION
Tokens in Command Buffer
ZTMF-TKN-TransID
specifies the transaction identifier of the transaction to be aborted.
ZTMF-MAP-Abort-Transaction
is an extensible structured token that contains fields for aborting a transaction.
Only one occurrence of this token is allowed. This token contains the following
fields:
ZIgnoreDataErrors
specifies whether or not data-related errors are to be ignored while the
specified transactions are being undone. This field is optional. If you do not
assign a value to this field, the default is ZSPI-VAL-False. The following values
are valid:
Normally, when the backout process encounters data errors while undoing a
transaction, it places the transaction in the hung state. When
ZIgnoreDataErrors is ZSPI-VAL-True, however, the backout process undoes as
much of the transaction as possible and, for those files yielding data errors,
ignores the errors as if the undo had been performed completely. If you omit
ZIgnoreDataErrors, the backout process reacts in the normal way,
acknowledging the errors and placing the transaction in the hung state.
ZAvoidHanging
specifies whether files that have data errors be noted and removed from
access while the specified transactions are being undone. The following values
are valid:
ZSPI-VAL-True
The backout process undoes as much of the transaction as possible. For
those files yielding data errors, the backout process writes an audit trail
record that preserves information about what parts of the transaction could
not be undone and marks the file “undo-needed,” so that it is no longer
accessible to applications. (To restore the file to the system, you must
typically use the file recovery process.) The backout process then aborts
the transaction.
ZSPI-VAL-True Data-related errors are ignored
ZSPI-VAL-False Data-related errors are not ignored
Caution. Contact the Global Customer Support Center (GCSC) or your service provider
before using this command with ZIgnoreDataErrors set to ZSPI-VAL-True.
This field can lead to database corruption and loss of data integrity. Include this field only if all
efforts to abort a transaction fail and data availability is more important than data integrity.