From:	CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX"  7-JUL-1989 15:58
To:	MRGATE::"ARISIA::EVERHART"
Subj:	RE: Copying tapes

Message-Id:  <8907071932.AA13773@crdgw1.ge.com>
Received: From KL.SRI.COM ([0.0.0.0]) by CRVAX.SRI.COM with TCP; Fri,  7 JUL 89 11:58:57 PDT
Received: from uoft02.utoledo.edu ([131.183.1.4]) by KL.SRI.COM with TCP; Fri, 7 Jul 89 11:43:03 PDT
Date: Fri, 7 Jul 89 14:27 EDT
From: Brian Nelson <BRIAN@uoft02.utoledo.edu>
Subject: RE: Copying tapes
To: INFO-VAX@KL.SRI.COM
X-Vms-To: IN%"INFO-VAX@KL.SRI.COM"


> Arthur Kendall <AJK@NIHCU.BITNET> write of a problem using vmstpc
> to go tape to tape

My apologies, I never did the code for tape to tape. Obviously trivial,
to write, but not having had two drives sortof precluded it. The program
should say something a bit more useful than 'tape to tape called'.
Actually, the program is optimized for tape to disk and then to back to
tape, to facilitate making multiple copies of tapes. It is very fast,
will stream tu81's, making use of up to 30 asynch qio's for reading a
tape and writing a tape. The major drawback is a blocksize limit of
32767, which is due to the use of rms11 for the disk container file

Would anyone be willing to implement the tape to tape function? And of
course, I'm open to any other suggestions for improvement. The current
source is online via vmsserv@uoft02, send an jnet message for bitnet
users:

$ send vmsserv@uoft02 vmsdump vmstpc.c

Internet users can send mail with the line

send vmstpc.c

Brian


