xref: /original-bsd/share/man/man4/man4.vax/ut.4 (revision c3e32dec)
1.\" Copyright (c) 1983, 1991, 1993
2.\"	The Regents of the University of California.  All rights reserved.
3.\"
4.\" %sccs.include.redist.man%
5.\"
6.\"     @(#)ut.4	8.1 (Berkeley) 06/05/93
7.\"
8.Dd
9.Dt UT 4 vax
10.Os BSD 4.2
11.Sh NAME
12.Nm ut
13.Nd
14.Tn UNIBUS TU45
15tri-density tape drive interface
16.Sh SYNOPSIS
17.Cd "controller ut0 at uba0 csr 0172440 vector utintr"
18.Cd "tape tj0 at ut0 drive 0"
19.Sh DESCRIPTION
20The
21.Nm ut
22interface provides access to a standard tape drive interface as
23describe in
24.Xr mtio 4 .
25Hardware implementing this on the
26.Tn VAX
27is typified by the System
28Industries
29.Tn SI
309700 tape subsystem.  Tapes may be read or written
31at 800, 1600, and 6250
32.Tn BPI .
33.Sh DIAGNOSTICS
34.Bl -diag
35.It tj%d: no write ring.
36An attempt was made to write on the tape drive
37when no write ring was present; this message is written on the terminal of
38the user who tried to access the tape.
39.Pp
40.It tj%d: not online.
41An attempt was made to access the tape while it
42was offline; this message is written on the terminal of the user
43who tried to access the tape.
44.Pp
45.It tj%d: can't change density in mid-tape.
46An attempt was made to write
47on a tape at a different density than is already recorded on the tape.
48This message is written on the terminal of the user who tried to switch
49the density.
50.Pp
51.It "ut%d: soft error bn%d cs1=%b er=%b cs2=%b ds=%b."
52The formatter indicated a corrected error at a density other
53than 800bpi.  The data transferred is assumed to be correct.
54.Pp
55.It "ut%d: hard error bn%d cs1=%b er=%b cs2=%b ds=%b."
56A tape error occurred
57at block
58.Pp
59.It bn.
60Any error is
61fatal on non-raw tape; when possible the driver will have retried
62the operation which failed several times before reporting the error.
63.Pp
64.It tj%d: lost interrupt.
65A tape operation did not complete
66within a reasonable time, most likely because the tape was taken
67off-line during rewind or lost vacuum.  The controller should, but does not,
68give an interrupt in these cases.  The device will be made available
69again after this message, but any current open reference to the device
70will return an error as the operation in progress aborts.
71.El
72.Sh SEE ALSO
73.Xr mt 1 ,
74.Xr mtio 4
75.Sh HISTORY
76The
77.Nm
78driver appeared in
79.Bx 4.2 .
80.Sh BUGS
81May hang if a physical error (non-data) occurs.
82