BSD 4_2 development

[unix-history] / usr / man / man4 / tm.4

.TH TM 4 "27 July 1983"
.UC 4
.SH NAME
tm \- TM-11/TE-10 magtape interface
.SH SYNOPSIS
.B "controller tm0 at uba? csr 0172520 vector tmintr"
.br
.B "tape te0 at tm0 drive 0"
.SH DESCRIPTION
The tm-11/te-10 combination provides a standard tape drive
interface as described in
.IR mtio (4).
Hardware implementing this on the VAX is typified by the Emulex TC-11
controller operating with a Kennedy model 9300 tape transport,
providing 800 and 1600 bpi operation at 125 ips.
.SH "SEE ALSO"
mt(1),
tar(1),
tp(1),
mtio(4),
ht(4),
ts(4),
mt(4),
ut(4)
.SH DIAGNOSTICS
\fBte%d: no write ring\fR.  An attempt was made to write on the tape drive
when no write ring was present; this message is written on the terminal of
the user who tried to access the tape.
.PP
\fBte%d: not online\fR.  An attempt was made to access the tape while it
was offline; this message is written on the terminal of the user
who tried to access the tape.
.PP
\fBte%d: can't switch density in mid-tape\fR.  An attempt was made to write
on a tape at a different density than is already recorded on the tape.
This message is written on the terminal of the user who tried to switch
the density.
.PP
\fBte%d: hard error bn%d er=%b\fR.   A tape error occurred
at block \fIbn\fR; the tm error register is
printed in octal with the bits symbolically decoded.  Any error is
fatal on non-raw tape; when possible the driver will have retried
the operation which failed several times before reporting the error.
.PP
\fBte%d: lost interrupt\fR.  A tape operation did not complete
within a reasonable time, most likely because the tape was taken
off-line during rewind or lost vacuum.  The controller should, but does not,
give an interrupt in these cases.  The device will be made available
again after this message, but any current open reference to the device
will return an error as the operation in progress aborts.
.SH BUGS
If any non-data error is encountered on non-raw tape, it refuses to do anything
more until closed.