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
Event Messages
HP NonStop TMF Management Programming Manual—540140-010
6-165
Descriptions of Event Messages
Effect
The transaction is retried or ignored, as indicated in the message.
If the status is “retried,” then the backout process terminates work on this transaction
and the TMF management process (TMP) resubmits the transaction identifier to the
backout process to try again to undo the transaction. If the TMP has already submitted
the transaction identifier to the backout process three times, then the TMP hangs the
transaction.
If the status is “ignored,” then the backout process ignores the error on the affected file
and continues to perform any other undo on behalf of the specified transaction.
Recommended Action
To determine if the transaction is “hung,” issue a STATUS TRANSACTION command,
specifying the particular transaction identifier.
If the transaction is “hung,” refer to the Guardian Procedure Errors and Messages
Manual to see if the file-system error can be corrected. If recovery is possible, perform
the corrective action, then issue a ABORT TRANSACTION command, specifying the
particular transaction identifier.
If the status indicated by this error message is “ignored,” then no recovery action is
immediately needed, but the affected file is not in a consistent state. If the problem
contact your service provider and provide all relevant information as follows:
Descriptions of the problem and accompanying symptoms
Details from the message(s) generated
Supporting documentation such as Event Management Service (EMS) logs, trace
files, and a CPU dump, if applicable
If your local operating procedures require contacting the Global Customer Support
Center (GCSC), supply your system number and the numbers and versions of all
related products as well.