Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!husc6!mit-eddie!ll-xn!nike!ucbcad!ucbvax!CU20B.COLUMBIA.EDU!SIT.BUSH
From: SIT.BUSH@CU20B.COLUMBIA.EDU (Nick Bush)
Newsgroups: mod.computers.vax
Subject: Re: Another terminal port problem....
Message-ID: <12254328007.23.SIT.BUSH@CU20B.COLUMBIA.EDU>
Date: Wed, 12-Nov-86 08:14:13 EST
Article-I.D.: CU20B.12254328007.23.SIT.BUSH
Posted: Wed Nov 12 08:14:13 1986
Date-Received: Wed, 12-Nov-86 22:04:26 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 23
Approved: info-vax@sri-kl.arpa

I ran into the same problem while doing almost exactly the same thing.
The problem occurs because of the way VMS and the PACX handle the port:

When no one has the port allocated under VMS and it is set to /MODEM, VMS
will keep DTR high, waiting for a phone call.  The PACX sees DTR high and
assumes that the terminal on the line (in this case the VAX) wants to talk
to it so it raises CD and DSR. VMS sees these, thinks the modem has answered
a phone call so it starts its timer waiting for someone to attempt to log in.
After nothing happens for a little while, the timer expires and VMS drops
DTR to hang up the phone.  After a couple of seconds, VMS will raise DTR
again, starting the loop all over again.

The solution to this is simple.  Set the permanent terminal characteristics
to /NOMODEM so that DTR will only be on when someone is actually trying to
use the port to "dial out (have your "KERMIT.COM" set /MODEM). You should 
also have the terminal set /NOTYPEAHEAD as a permanent characteristic and
set /TYPEAHEAD in your command file.  This will avoid any possibility of
a loop between the PACX and the VAX.

- Nick Bush
  SIT.BUSH@CU20B.COLUMBIA.EDU
  SIT.BUSH@CU20B (BITNET)
-------