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!ucbvax!seismo.css.gov!munnari!summer.su.oz!richardson_j
From: richardson_j@summer.su.oz.UUCP
Newsgroups: mod.computers.vax
Subject: Re: interpreting show err reports for terminal ports
Message-ID: <8511091541.AA13937@seismo.CSS.GOV>
Date: Sun, 10-Nov-85 00:54:01 EST
Article-I.D.: seismo.8511091541.AA13937
Posted: Sun Nov 10 00:54:01 1985
Date-Received: Sun, 10-Nov-85 09:30:29 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 28
Approved: info-vax@ucbvax.berkeley.edu

[]

We used sometimes to get thousands of errors on our terminal ports, which
are Able VMZ32Ns, until we took Kevin Carosso's advice and set the SYSGEN
parameter TTY_DEFPORT (new in VMS V4.1: not TTY_DEFPROT) to 1.  This stops
VMS using the "AUTOXON" feature which (perhaps) works on DEC's DMF-32 but
doesn't on VMZs.  Thanks, Kevin!

We then got dozens of errors until we took Reinhard Goeth's advice and set
/DMA on the VMZ lines.  This is most easily done by altering the SYSGEN
parameter TTY_DEFCHAR2 so that bit TT2$M_DMA = 64 is set; e.g. change it
from the default value 4098 to the value 4162.  As mentioned in a recent
Software Dispatch (July?), the default in VMS V4 is /NODMA, unlike V3,
and contrary to the documentation in the Terminal Driver chapter of the I/O
User Manual.  Thanks, Reinhard!

Now we only get a few terminal errors per month.

(Is everyone on Usenet aware that because of a bug in the setting up of
the new mod.computers.vax arrangements, one may not see one's own articles,
and neither may other news readers along the mail path from originator to
sri-kl?)

--
Jim Richardson
Department of Pure Mathematics, University of Sydney, NSW 2006, Australia
UUCP:	...!seismo!munnari!summer.oz!jimr
ARPA:	jimr%summer.oz@seismo.arpa		CSNET:	jimr@summer.oz