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-173
STATUS DATAVOLS
ZTMF-VAL-DVS-AwaitTransResolve
specifies configured data volumes that are being restarted, where the
restart is waiting for the resolution of transactions that may have modified
data on the volume. The subsystem must be notified of the outcome
(commit or abort) of these transactions before these volumes can take part
in recovery. A data volume can linger in this state if lengthy transactions
exist in the system or if the outcome of a distributed transaction cannot be
determined.
ZTMF-VAL-DVS-QueuedForRecovery
specifies configured volumes that are ready for volume recovery but are
waiting for process availability. A data volume remains in this state until it is
assigned to a volume-recovery process. The data volume might have to
wait for an existing volume recovery to complete.
ZTMF-VAL-DVS-Recovering
specifies configured volumes that are being operated on by a volume-
recovery process.
ZTMF-VAL-DVS-StartupCompleting
specifies configured volumes for which startup is nearly complete. The
associated disk process is processing the final startup request. Typically, a
data volume remains in this state only very briefly.
ZTMF-VAL-DVS-Started
specifies configured volumes that are ready to process TMF transactions.
Audited requests are allowed only for data volumes in this state as long as
transaction processing is enabled within the subsystem.
ZTMF-VAL-DVS-NotStarted
specifies configured volumes that are not in the started state.
ZTMF-VAL-DVS-Down
specifies configured volumes that are in either the down-clean or down-
dirty state.
ZTMF-VAL-DVS-Down-Clean
specifies configured volumes that are inaccessible, perhaps because of
device or process problems, and on which no updates have been made to
audited files since the volume last underwent a clean shutdown. Audited
files on volumes in this state do not contain any inconsistencies.










