[Info-vax] Newbie: change console port speed
John Wallace
johnwallace4 at yahoo.co.uk
Thu Aug 27 07:36:18 EDT 2009
On Aug 27, 12:34 am, David J Dachtera <djesys... at spam.comcast.net>
wrote:
> Slor wrote:
>
> > I'm guessing someone here can quickly answer a question I've been combing
> > the FAQs for the answer to (and probably overlooking). If possible, I'd
> > like to increase the default speed of my serial console higher than 9600
> > for my AlphaServer 600. If it matters, I'm running OpenVMS 8.3. Someone
> > got a quick bit of insight for me there?
>
> Depending what your need is, that might not be a good idea.
>
> If the issue is that OPCOM is getting backlogged to the point where it
> hangs and/or the console is rendered useless, a better solution would be
> to keep OPA0: disabled as an OPCOM terminal and assign that instead to
> something much faster. If OPERATOR.LOG does not provide the data you
> need, you may need to explore other options.
>
> Speaking from experience here. Oracle on VMS is very chatty about a lot
> things, and that can cause the console of GS1280 to get hosed up royal.
> Where possible, I connect to the console from an MBM session started
> over TELNET, so OPCOM data can be displayed at ethernet speed rather
> than be limited to the baud rate of the serial console.
>
> If you're seeing device timeout errors on OPA0:, you'll want to explore
> other options.
>
> D.J.D.
There is a world of difference between serial console IO hardware on a
GS1280 and serial console IO hardware on an AlphaServer 600 or other
representative AlphaStation/AlphaServer.
A GS1280 has more buses and complexity than you can shake a stick at,
and lots of good reasons to avoid console IO.
An AlphaServer 600 or similar box has a CPU, a CPU->IO chipset, and
(iirc) a SuperIO/JunkIO chip including a couple of comms ports.
There might be a bit more to it than that in boxes with the smart
console stuff, but iirc the AlphaServer 600 isn't one of them.
More information about the Info-vax
mailing list