Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!ucbvax!GRINNELL.MAILNET!McGuire_Ed
From: McGuire_Ed@GRINNELL.MAILNET.UUCP
Newsgroups: mod.computers.vax
Subject: Re: reassignment in VMS
Message-ID: <8702050850.AA03061@ucbvax.Berkeley.EDU>
Date: Wed, 4-Feb-87 10:59:00 EST
Article-I.D.: ucbvax.8702050850.AA03061
Posted: Wed Feb  4 10:59:00 1987
Date-Received: Sat, 7-Feb-87 10:48:53 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 13
Approved: info-vax@sri-kl.arpa

Now, Carl, I think your reaction was in poor taste.  Not only are you unlikely
to make a friend that way, I disagree with your assertion that it is obvious
that SYS$ASSIGN assigns channels to devices, not files.  Anyone who has only
used the I/O operations built-in to a HLL would assume that you can assign a
channel to a file on a device using SYS$ASSIGN, because that's the way it works
with HLL channel assignment.

I do agree completely that one should stick with the HLL I/O statements unless
it is very difficult or impossible to get from here to there with them.  The
next step is indeed RMS, and then the ACP QIO interface.  I wish the original
posting had explained why the author had given up on FORTRAN I/O.

Ed