🚀 go-pugleaf

Dear Net.Decus:

Is there a way I can squelch the continual respawning of LOGINOUT at a VMS
terminal line which would otherwise be excited by characters coming at it
when it is not allocated or otherwise in use?  I have a terminal line which
I want to connect to Datakit as an outgoing port, to be used only as initiated
from inside the VAX, not from the Datakit line.  But I want then to use it for
two-way communication (not like a spooled printer or the like).  I have tried
things like $ set terminal /nointeractive device:  which does not seem to
work.  The problem with having LOGINOUT at the terminal is that it keeps having
a constant conversation with Datakit, with a lot of Username:  Password:
User authorization failure while Datakit is going Username: IS AN INVALID
DESTINATION  Password: IS AN INVALID DESTINATION  User authorization failure
IS AN INVALID DESTINATION with the result that VMS and Datakit are driving each
other wild.  This leads to difficulties when the terminal is to be allocated,
from a batch job.  (I solve it by sitting in a loop trying to allocate the
sucker until I catch it at just the right time or have tried a couple of
hundred times with no luck).

Any clues or help would be mucho appreciated.  Thanks much.
-- 
 -------------------------------    Disclaimer:  The views contained herein are
|       dan levy | yvel nad      |  my own and are not at all those of my em-
|         an engihacker @        |  ployer, my pets, my plants, my boss, or the
| at&t computer systems division |  s.a. of any computer upon which I may hack.
|        skokie, illinois        |
 --------------------------------   Path: ..!ihnp4!ttrdc!levy
                                      or: ..!ihnp4!iheds!ttbcad!levy