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!cbosgd!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: aborting asyncronous RMS IO
Message-ID: <5995@ucbvax.ARPA>
Date: Wed, 3-Apr-85 16:54:18 EST
Article-I.D.: ucbvax.5995
Posted: Wed Apr  3 16:54:18 1985
Date-Received: Fri, 5-Apr-85 02:06:38 EST
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 16

From: Provan@LLL-MFE.ARPA


Well, I'm not sure if I seldom get answers because my questions are too
hard or too easy, or just because nobody likes me.  But since I
sometimes do get answers....

From what I can tell, there are only two ways to "abort" an RMS IO once
it's started.  One is by calling Sys$RMSRunDown (a co-worker claims to
be having problems even getting that to abort an outstanding terminal
input wait).  The other is to issue a $Cancel on the Fab's channel from
executive mode, which I assume will work although I haven't tried it
yet.  Am I missing some normal way of telling RMS to cancel all active
IO for a particular Rab or a particular Fab?  I'm not real thrilled
about giving CMExec privs to user programs and Sys$RMSRunDown will
close Fab's I don't want to close.