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
Error and Warning Messages
HP NonStop TMF Management Programming Manual—540140-010
7-61
Archive Tape Errors and Warnings
8063 Tape format is bad (An EOF mark was found where an end volume
label was expected).
The tape format is invalid. This could be caused by corruption of the tape, dirty
tape drive heads, faulty tape drives, or a software bug in the dump or restore
program.
8064 Tape format is bad (An EOF mark was found where a file label or an
end volume label was expected).
The tape format is invalid. This could be caused by corruption of the tape, dirty
tape drive heads, faulty tape drives, or a software bug in the dump or restore
program.
8065 Tape format is bad (An EOF mark was found where a file label
continuation record was expected).
The tape format is invalid. This could be caused by corruption of the tape, dirty
tape drive heads, faulty tape drives, or a software bug in the dump or restore
program.
8066 Tape format is bad (An EOF mark was found where a data block
record was expected).
The tape format is invalid. This could be caused by corruption of the tape, dirty
tape drive heads, faulty tape drives, or a software bug in the dump or restore
program.
8067 Tape format is bad (Variable-length termination record was not on
the same tape as the last data block of the file).
The tape format is invalid. This could be caused by corruption of the tape, dirty
tape drive heads, faulty tape drives, or a software bug in the dump or restore
program.
8068 Tape format is bad (An EOF mark that terminates a file was not
found).
The tape format is invalid. This could be caused by corruption of the tape, dirty
tape drive heads, faulty tape drives, or a software bug in the dump or restore
program.
8069 Tape format is bad (Two tape EOFs were not found at the end of the
tape).
The tape format is invalid. This could be caused by corruption of the tape, dirty
tape drive heads, faulty tape drives, or a software bug in the dump or restore
program.