🚀 go-pugleaf

 I'm posting this message to try to determine which other sites are
 having trouble connecting ISNs to VAXes via DMZ boards.  I have been 
 in contact with an AT&T tech. support person who is working on the 
 problem.  I thought it might help to have of list of interested parties
 to facilitate distributing any fixes or work-arounds that surface.
 Also, AT&T is interested in getting some estimate of how may sites
 are affected.  So if you are experiencing the problem described below,
 please send me a message via E-mail.  Please include the name(s) of
 the people at your site to whom information on this topic should be
 sent.  The VAX in question here at JHU is an 8600 running VMS, but
 other 11/78x class sites have reported similar troubles.

 The problem that we (and several other ISN sites) are having is that
 ISN lines connected to our VAX via DMZ-32 boards display cursor movement
 escape sequences on the terminal in some cases.  For example, when in
 EDT in full screen mode, holding down one of the cursor movement keys
 will correctly handle some of the escape sequences (and move the cursor)
 but sometimes the escape sequence ends up in the file.  This problem
 does *not* happen when connecting an ISN via DMF boards.  In addition
 we have had this problem when using two versions of VMS, 4.1a and 4.3.

 AT&T suggested that I change the endpoint characteristics for the VAX/8600
 ports to "2 stop bits" to reduce the frequency of the escape sequence
 problem.  This does seem to have helped although I can still reproduce
 the error. I would suggest trying this as it does make full screen editing
 workable if not perfect.

 -jj

 USENET:   ihnp4!whuxcc!jhunix!ecf_ujaj
 ARPA:     jones@hopkins
 BITNET:   L64A0110@jhuvm
 CSNET:    jones%hopkins.arpa@csnet-relay