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-157
Descriptions of Event Messages
Effect
The effect of this event depends on which recovery process was used.
For backout, this event message is accompanied by a second event (171 or 172) that
indicates the effect.
For volume or file recovery, this event message is accompanied by event 171. The file
is marked either “redo-needed” or “undo-needed” and is no longer available for
transaction processing.
Recommended Action
If the backout process was involved and the event message is accompanied by event
172, then some type of recovery action may be required, depending upon the status
indicated by event 172. If the status is “ignored,” then no recovery action is needed
immediately (although the affected file is no longer consistent). If the status is “retried,”
then no recovery action is needed unless the transaction becomes “hung.” In the latter
case, refer to the Guardian Procedure Errors and Messages Manual for corrective
action for the indicated file-system error number.
If either the volume recovery process or the file recovery process was involved, then
the event is serious and file recovery is needed.










