Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site wdl1.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!hao!hplabs!hpda!fortune!wdl1!jbn
From: jbn@wdl1.UUCP
Newsgroups: net.unix-wizards
Subject: Re: Tape Labels
Message-ID: <378@wdl1.UUCP>
Date: Tue, 16-Apr-85 21:24:58 EST
Article-I.D.: wdl1.378
Posted: Tue Apr 16 21:24:58 1985
Date-Received: Sat, 20-Apr-85 03:05:51 EST
Sender: notes@wdl1.UUCP
Organization: Ford Aerospace, Western Development Laboratories
Lines: 19
Nf-ID: #R:brl-tgr:-992800:wdl1:17100078:000:1077
Nf-From: wdl1!jbn    Apr 16 18:10:00 1985


     Actually, when it is all fully supported, mandatory tape labeling is
very convenient.  The user calls for a tape file by giving a list of reel
numbers, the order for the operator to mount the tape appears on the console,
the reel number appears in illuminated numbers atop the tape drive, one of
the operators puts the tape on the drive and pushes the LOAD button, the
drive closes the door, removes the tape seal, threads the tape, reads the
first block, and checks the label; if it's the wrong tape, the drive unloads
the tape, opens the door, and logs the wrong mount in the system log for later
operator discipline, then calls for the right tape again.
    When you get to the end of a reel, the next tape gets mounted without
the application program even being aware that a reel break occured.  When
writing, new blank tapes are allocated and labels printed automatically as
writing continues over reel boundaries.
    I'm describing a big UNIVAC mainframe shop here; IBM operations are
similar.  But this is what tape is like in the big tape shops.

					John Nagle