Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!rutgers!ucla-cs!zen!ucbvax!GRIN2.BITNET!MCGUIRE From: MCGUIRE@GRIN2.BITNET.UUCP Newsgroups: comp.os.vms Subject: RE: Reading past a tapemark Message-ID: <8708040324.AA15879@ucbvax.Berkeley.EDU> Date: Sat, 1-Aug-87 16:40:00 EDT Article-I.D.: ucbvax.8708040324.AA15879 Posted: Sat Aug 1 16:40:00 1987 Date-Received: Wed, 5-Aug-87 03:08:34 EDT Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 26 > Date: Tue, 28 Jul 87 15:12:54 EDT > From: "Mary E. Bainter" > Subject: Reading past a tapemark > > I have a tape with two files on it, separated by a tapemark. There is really > only data in the files, i.e. without fileheaders or names of files COPY can read this type of file onto disk, provided that you inform it what the tape recordsize and blocksize are. You might do the following commands. $ ALLOCATE drive TAPE $ MOUNT/FOREIGN/RECORDSIZE=r/BLOCKSIZE=b TAPE $ COPY TAPE: FILE.1 $ COPY TAPE: FILE.2 If the record- and blocksize is different for the second file, you can dismount the tape and remount it with different values, then use SET MAGTAPE to skip to the second file before using COPY. Look at SET MAGTAPE for more information. > I have been able to read up to the first tapemark using MUMPS (our application > language) You can read the second file only if MUMPS does not rewind when you access the tape drive. If it doesn't rewind, you should be able to read the first file, then when you hit end-of-file close the file, then open the second file and read it. ---- Ed McGuire, Systems Coordinator, Grinnell College, MCGUIRE@GRIN2.BITNET