CHRIS@ACRUX.USC.EDU.UUCP (06/12/87)
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> We're running VMS 4.4 with STC tridensity drives on Emulex controllers. -------
helen@uhccux.UUCP (06/14/87)
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:
ESCFLASS@UBVM.BITNET ("Mr. Peter Flass") (06/22/87)
>> > Does anyone other than me have problems with end-of-tape processing? ... >from what I have seen it appears that the MTAACP doesn't do the Right >Thing on reads. I experienced a problem restoring a file from a saveset which spanned two reels. Backup got to the end of the first reel and refused to continue. I could not get it to accept the second reel. Naturally I thought this was something I was doing wrong... (We are running VMS 4.3 and using TU80's for backup) Pete Flass Empire State College