Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 alpha 4/15/85; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: God *Dammit*
Message-ID: <8537@ucbvax.ARPA>
Date: Wed, 26-Jun-85 22:44:34 EDT
Article-I.D.: ucbvax.8537
Posted: Wed Jun 26 22:44:34 1985
Date-Received: Thu, 27-Jun-85 07:46:59 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 19

From: *Hobbit* 

It seems that interrupt character handling across DECNET has changed
wildly under 4.0VMS.  If you do SET HOST , log in, and then
run some program at the remote end, you look fine until you type a ^C,
whereupon you get DCL back.  Okay, you say, that's what is supposed to 
happen, so why complain?  Well, if I am running Telnet at the far end,
^C is supposed to be transmitted *through* that far end Telnet and be 
passed on to wherever I am Telnetted to.  Instead, REMACP or RTdriver
or whatever generates a $FORCEX for the image I am running.  Unconditionally.
This not only blows my TN connection away but leaves my terminal in
strange states, as one might expect.

Under 3.x this doesn't happen; the remote AST delivery mechanism functions
properly.  This FORCEX trash is in direct violation of what a ^C AST is
supposed to do.  Is there a way around it????

_H*
-------