Xref: utzoo bit.listserv.ibm-main:2205 comp.protocols.ibm:1785
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!uwm.edu!convex.csd.uwm.edu!dave
From: dave@convex.csd.uwm.edu (David A Rasmussen)
Newsgroups: bit.listserv.ibm-main,comp.protocols.ibm
Subject: Terminal Parity woes
Message-ID: <12215@uwm.edu>
Date: 17 May 91 16:59:30 GMT
Sender: news@uwm.edu
Followup-To: bit.listserv.ibm-main
Distribution: na
Organization: UW-Milwaukee Computing Services Division
Lines: 22
Originator: dave@convex.csd.uwm.edu


Our campus has 100's of terminals at various sites that talk to all our hosts
up til now at no parity. Recently our School of Business installed a IBM 9000
with a "6445 protocol converter". Some of our terminals are soft setup so that
users can switch the settings, and our unix machines don't really care how some
terminals are set, but we have a number of ancient terminals that we may have to
replace.


We asked the people installing things about whether the 9000 or converter could
be strapped at a hardware level for no parity, but it is my impression that 
these people are merely "install by number" people. Does anyone out there know
if the 9000 or this series protocol converter be configured to work with
terminals configured for no parity?


Has anyone else addressed this problem that can make some suggestions?

-- 
Dave Rasmussen - Systems Programmer/Manager, UW-Milwaukee Computing Svcs Div.
Internet:dave@uwm.edu, Uucp:uwm!dave, Bitnet:dave%uwm.edu@INTERBIT
AT&T:414-229-5133 USmail:Box 413 EMS380,Milwaukee,WI 53201