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-85
DUMP FILES
A value of 2 is recommended in case one tape cannot be read because of a
tape media failure, or if each copy of the dump requires multiple tape volumes.
ZBlockSize
for dumps to tape, sets the tape data block length, when multiplied by 1024
bytes. It is more efficient to use large data block lengths, but this is limited by
the density in bits per inch (bpi) at which the tape drive writes tapes. The
following values are valid; the default is 8:
ZVerifyTape
for dumps to tape, specifies whether tape verification is performed after a tape
is written. The following values are valid:
ZSPI-VAL-True
Tapes are verified. After each tape volume is written, it is rewound, read
completely, and finally rewound and unloaded. The tape-record
checksums, tape-record sequence numbers, and tape format are verified.
The checks are the same as those made during file recovery; however,
tape verification does not include comparing the tape data to the audit trail
files on disk.
If tape verification fails, an error is returned, the online dump terminates,
and the online dump copy is marked invalid in the catalog. Tape verification
approximately doubles the time needed for a dump.
ZSPI-VAL-False
Tapes are not verified.
If you omit this field, its default value is ZSPI-VAL-False.
4 Tape data block length of 4096 bytes (800 bpi); recommended.
8 Tape data block length of 8192 bytes (1600 bpi); recommended.
12 Tape data block length of 12288 bytes.
16 Tape data block length of 16384 bytes.
20 Tape data block length of 20480 bytes.
24 Tape data block length of 24576 bytes.
28 Tape data block length of 28672 bytes (6250 bpi); recommended.