Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!ptsfa!ames!sdcsvax!nosc!humu!uhccux!helen
From: helen@uhccux.UUCP
Newsgroups: comp.os.vms
Subject: Re: end-of-tape processing
Message-ID: <591@uhccux.UUCP>
Date: Sun, 14-Jun-87 00:57:48 EDT
Article-I.D.: uhccux.591
Posted: Sun Jun 14 00:57:48 1987
Date-Received: Tue, 16-Jun-87 01:25:12 EDT
References: <SUN-MM(195)+TOPSLIB(124).11-Jun-87.18:52:34.ACRUX.USC.EDU>
Organization: U. of Hawaii, Manoa (Honolulu)
Lines: 18
Summary: Try this instead

In article <SUN-MM(195)+TOPSLIB(124).11-Jun-87.18:52:34.ACRUX.USC.EDU>, CHRIS@ACRUX.USC.EDU (Christopher Ho) writes:
> Does anyone other than me have problems with end-of-tape processing?
> Imagine the following sequence:
> 	$ mount/init=cont mta0: foo
> 	$ copy/log t.tmp mta0:*.*	! very large file
> 	<reach end of tape, operator mounts next reel, gives REPLY/TO=n>
> 	$ dismount mta0:
> 	$ mount mta0: foo	! first tape again
> 	$ copy/log mta0:*.* *.*
> 	<tape spins merrily along, reaches the end, runs off the reel>

If you are using the tape in house or sending to a site running VMS
try this instead:

$ mount/for mta0:
$ backup/rewind/log t.tmp mta0:foo/save_set     ! you could have a /den=
$!                                                to 1600 or 6250.
$ dismount mta0: