Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!ucbcad!ucbvax!EMX.CC.UTEXAS.EDU!kneuper
From: kneuper@EMX.CC.UTEXAS.EDU (Steve Kneuper)
Newsgroups: comp.os.vms
Subject: (none)
Message-ID: <8801071902.AA15677@emx.utexas.edu>
Date: 7 Jan 88 19:02:43 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 21


[my first posting, after two years of reading...] 

My async ports get into a funny state - where they start accumulating errors
(about one a second) and pumping out nulls and line feeds (not quite sure) at a
slow rate (also about one a second).  The user using the port has no way to get
out of whatever program he/she is running - since the user connects via a MICOM
port selector they punch the <break> key a bunch of times to get back out to
the MICOM prompt, were they start another session with VMS... once I notice the
problem I kill the user job and set the port /NOMODEM to make the MICOM not
connect other users to the port. 

Since I upgraded to 4.6 this has happened on a more frequent basis - two or
more times daily versus once every two weeks.  Has anyone else dealt with
something resembling this?  To my knowledge, this problem does not occur
on the rest of the University of Texas - Austin vaxen hooked to the micom
system.

Steve Kneuper                             kneuper@emx.cc.utexas.edu - ARPAnet
University of Texas System                xxss521@utchpc            - BITNET
Center for High Performance Computing     utchpc::xxss521           - THEnet