Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!watmath!clyde!cbosgd!ulysses!ucbvax!info-vax
From: MORSE@NSFVAX.BITNET
Newsgroups: mod.computers.vax
Subject: X-off Problem (help wanted)
Message-ID: <8601080957.AA08624@ucbvax.berkeley.edu>
Date: Wed, 8-Jan-86 04:57:38 EST
Article-I.D.: ucbvax.8601080957.AA08624
Posted: Wed Jan  8 04:57:38 1986
Date-Received: Thu, 9-Jan-86 00:07:26 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 34
Approved: info-vax@sri-kl.arpa

We are having a problem with our VAX that DEC cannot solve.
Perhaps someone on the net has some information?

We have a VAX 785 running VMS.  It has two DHU11's.  Terminal
access is at 9600 baud and goes through a MICOM 600 port
selector.  What happens is that one of the ports refuses to
accept characters, meaning you cannot log on to it.  After every
character (or couple of characters) the port transmits an X-off
to the terminal, and the terminal refuses to transmit anything
more to the VAX.  The user sees the Username: prompt, but after
the first character of their username is echoed back, it appears
as if everything is hung.  If the terminal is set to ignore the
X-off, the user can log on and the session is completely normal
except that the VAX continues to send X-off's every few
characters.

This appears pretty infrequently, but usually one line will go
weird within a week after a boot, which seems to clear up the
problem.  Once a line exhibits the problem, it remains that way
until a system boot.  The problem does not hit one particular
line, it seems relatively random.

Anybody every see this before?  Any ideas?  It's getting to be a
pain to disable the ports at the port selector.  DEC has pretty
much given up, although they suspect it is something the MICOM is
doing.

Thanks in advance,
Mike Morse

National Science Foundation

BITNET:   MORSE@NSFVAX
CSNET:    MORSE@NSF