Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!ihnp4!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: asyncronous 's?
Message-ID: <5885@ucbvax.ARPA>
Date: Fri, 29-Mar-85 13:20:55 EST
Article-I.D.: ucbvax.5885
Posted: Fri Mar 29 13:20:55 1985
Date-Received: Sat, 30-Mar-85 01:30:09 EST
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 29

From: Provan@LLL-MFE.ARPA


Hello!  Me again!

I've just noticed that despite the encouraging completion routines,
it's not possible to indicate to RMS that an $Open is to be done
asyncronously.  Normally, of course, one doesn't notice this, but I'm
trying to do an $open over DecNet where the delay can be several
seconds.  Since the program in question has many other things to do
while it's waiting, it's really unhealthy for it to sit around
twiddling its thumbs even long enough for local IO generated by the
$open to complete, let alone wait for the remote process to fire up and
all that.

First off, am I missing a way to make $open's asyncronous?

If not, does DEC recognize this as a deficiency?

If so, are they planning on fixing it, or is it not fixable?

Since I got jumped on last time for not being specific about what I
wanted to know, let me just make it clear that I recognize that there
are ways to make the DecNet $open faster (like setting up permanent
server processes and such).  That's not the issue.  If there were no
DecNet involved, I'd still be waiting for IO to complete when I don't
want to.  I'm *only* interested in information about the asycronous
question.  All other questions I already know the answer to.  (If you
believe that, you've only been on this list a couple of days....)