Guardian Programmer's Guide

Table Of Contents
Communicating With Magnetic Tape
Guardian Programmer’s Guide 421922-014
12 - 87
Recovering From “Device Not Ready” Errors
Recovering From “Device Not Ready” Errors
The system returns error 100 for several reasons: the tape unit is not powered up,
there is no tape on the drive, or the tape is currently rewinding. Your program should
retry the operation when the errant condition is fixed. Typically the fix requires human
intervention, so it would be appropriate to prompt the user before retrying the
operation.
Recovering From Tape Unit Power Failure
If the power to a magnetic tape unit fails and the application attempts a read, write, or
control operation, then one of the following errors is returned: file-system error 100
Table 12-4. Commonly Encountered Tape Errors
File System
Error Number Caused by...
1 Read reached end of file (EOF) or write reached end of tape (EOT)
2 Invalid operation for a tape drive
21 Illegal count specified; attempt was made to transfer large data or not
en
ough data
28 Too many outstanding nowait operations
40 Operation timed out
60 Device down or not open
66 Device down
100 Device not ready or controller not operational
101 Tape write protection is on
120 Data parity error, or attempt to access a tape whose density is higher
t
han the switch setting on the tape drive
150 End of tape sticker detected
151 Runaway tape condition or incorrect tape density
153 Tape drive power on
154 BOT encountered during backspace files or backspace records
156 Tape command rejected
188 Data lost, especially when buffering is on
190 Device error; hardware problem
193 Invalid or missing microcode file
214 Channel timeout (hardware error)
218 Interrupt timeout
224 Controller error
200 through 255 Path errors