iglesias@UCI.EDU (Mike Iglesias) (11/14/85)
I finally found what is causing the strange autobaud problem I was (and
still am having). It is occuring on both a 780 and a 785 running v4.1
and using DZ-11s. I found a way to cause the problem by doing the
following:
1. Connect to a line at 300 baud.
2. Type <cr> twice. Three times and VMS figures out the baud rate and
gives me the logon message.
3. Disconnect from the line.
4. Reconnect at 9600 baud. Typing <cr>s doesn't autobaud; VMS times
out the connection and drops the line after 30 seconds.
What I have been able to figure out from the fiche is that the line
speed is not reset to 9600 baud on a new connection if it's set to 600
baud. Here's what the autobaud code seems to do:
1. If the speed is not 9600 or 600 baud, set it to 9600.
2. See if the character typed is recognized in the 9600 baud table
(handles baud rates from 1200-9600).
3. If not, something changes to baud rate to 600 baud; the next character
typed is checked against the 600 baud table (handles 50-1200 baud).
4. If BREAK is hit, toggle between the 9600 and 600 baud tables (and
set the line speed accordingly).
This is why hitting BREAK solved the problem we are having. Now, if
anyone knows where the baud rate gets switched to 600 baud, please let
me know. I also can't find where the line is set to a known state
on a connection (speed, parity, etc). I'd like to know where that
is done also, mostly for my information.
We have TTY_DIALTYPE set to 2 as our Develcon dataswitch needs full
modem control to make the connection (it raises RI, VMS responds with
DTR & RTS, etc).
My SPR to DEC will be sent out soon.
Mike Iglesias
University of California, Irvine