Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!ames!ucbcad!ucbvax!VLSI.JPL.NASA.GOV!tencati
From: tencati@VLSI.JPL.NASA.GOV (Ron Tencati)
Newsgroups: comp.os.vms
Subject: Re: SET HOST/DTE
Message-ID: <871103223405.05b@VLSI.JPL.NASA.GOV>
Date: Wed, 4-Nov-87 01:33:50 EST
Article-I.D.: VLSI.871103223405.05b
Posted: Wed Nov  4 01:33:50 1987
Date-Received: Tue, 10-Nov-87 07:19:35 EST
Sender: usenet@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 29

At my site, we have noticed a bug in RTPAD that has existed since V4.4:

A user on some remote node does a SET HOST and logs onto my node, then once
logged in issues a SET HOST/DTE command to one of the out-going modem or asynch
LAN ports.  RTPAD connects to the specified port, but there is some kind of I/O
error reported (exact text escapes me at the moment...).  The user has a normal
session with the out-bound port, then types ^\ and logs off my machine.

According to my machine, the user is still logged in, NCP shows an active
link from the remote node, and the user process on my machine is running RTPAD 
in some sort of loop that is consuming a LOT of CPU time.

I have had jobs consume inordinate amounts of CPU time when this bug is
activated.  This behavior is about 75% reproducable.  

I brought this issue up at the DECUS in SF last year, and I was told that "DEC
had recently discovered this problem, and they would look into it".  That is
the last I heard from them. 

This may be related to the problem you are having with RTPAD.  I can't offer
you any solution, only provide you with my experience. 

I don't know if this "feature" is fixed under V4.6, DEC???


                                            Ron Tencati
                                            System Mgr.
                                            JPL-VLSI.ARPA
                                       Jet Propulsion Laboratory