Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-lcc!mordor!styx!ames!ucbcad!ucbvax!UORDB2.BITNET!JCOV
From: JCOV@UORDB2.BITNET
Newsgroups: mod.computers.vax
Subject: re: ds names on tape
Message-ID: <8612310020.AA01023@ucbvax.Berkeley.EDU>
Date: Sat, 27-Dec-86 04:38:00 EST
Article-I.D.: ucbvax.8612310020.AA01023
Posted: Sat Dec 27 04:38:00 1986
Date-Received: Wed, 31-Dec-86 00:40:38 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 84
Approved: info-vax@sri-kl.arpa

> Hi John,
>
>        Regarding your ANSI tape problem, I have ran into similar
>        situations before. I was trying to read an ANSI tape written
>        by a PDP-15 running RT-11 on a VAX running VMS. The directory
>        of the tape looks exactly what you described: file names with
>        quotes around them. This is because the names written by the
>        "foreign" machine is right-justified (does your file names
>        look like "FILE  .DAT" ?) and VMS don't like that.
>
>        Now working from memory, I did the following to copy the whole
>        tape:
>
>                $mount/foreign ...
>                $copy tape_drive: header.file
>                $copy tape_drive: eof1
>                $copy tape_drive: eof2
>                $copy tape_drive: file1.dat
>                $copy tape_drive: eof1
>                $copy tape_drive: eof2
>                $copy tape_drive: file2.dat
>                        .
>                        .
>                        .
>
>
>        The header.file contains the ANSI tape label, followed by two
>        end-of-file marks, then comes the first file, followed by two
>        more eof marks, then the next file, two eof marks, etc. ....
>
>        The number of EOF marks between files may be only one, depending
>        on the source machine (one Honeywell system I used allowed me an
>        option of one or two EOF marks!). I actually had the copy commands
>        all in a command procedure, generated using a quick-and-dirty
>        FORTRAN program. Don't have a loop in the procedure to do the
>        copying as I am not sure how copy or VMS would handle the
>        end-of-tape! Its better just to put in as many copy commands as
>        you need and no more.
>
>        The trick here is to fool VMS into not grabbing the tape label then
>        using the fact that each copy command stops at an eof mark. I tried
>        this under VMS v3 and have not tried it under v4.
>
>        Let me know if this works for you or not. If not, I'll think of
>        something else. If it works, please post it to Netland. Again, I'm
>        writing this from memory, so if it doesn't work, let me know and
>        I'll dig up my notes/log files.
>
>        Good luck!
>
>
>-------------------------------------------------------------------------------
>Peter Kuo                      Bitnet (VMS address)  : KUO@SASK
>Accelerator Laboratory                (UUCP address) : "skatter!kuo@sask.uucp"
>(a.k.a. The Beam Warehouse)
>Univ. of Saskatchewan            uucp (unix address) : !ihnp4!sask!skatter!kuo
>Saskatoon, Saskatchewan
>CANADA  S7N 0W0
>Tel. (306) 966-6059
>
>[Disclaimer: all the standard stuff.]
>
>
>p.s. Just as a matter of interest, what machine wrote your tape and what did
>     your file names look like?


   No, my file names were not right justified.

   Also, your letter implies that you can mount a tape as foreign
and then issue copy commands from the tape.

   What names do you use for the copy commands from the
tape?   The copy doc says nothing about doing
any such thing and I wonder how its done.

   The name that crapped out my system did not have any quotes at
all by the way.


   Thanks much.


         John Covici