Re: 504

Keep in mind that the console cable and connection is an initial boot
protocol.  It has to work every time, no bugs, probably minimal security,
...

Adding "reconnect after the cable has been disconnected" functionality will
increase the complexity of the protocol, theoretically make it more likely
to fail.   That would defeat its purpose:  be there when the system boots.

also, consider being the ibm programmer responsible for the console
connection.  If the connection is not made the system is inaccessible.  You
might want to shut down all other activity of the cpu until the connection
is reestablished, continuously poll the cable port.   If so, do you then
have to add "dont dedicate all resources to reestablishing the connection if
the system is already up" code to the protocol if a reestablish the
connection feature is added to the protocol ??


Steve Richter


----- Original Message -----
From: "Leif Svalgaard" <leif@leif.org>
To: <midrange-l@midrange.com>
Sent: Thursday, March 14, 2002 12:44 AM
Subject: Re: 504


> From: Steve Richter <srichter@autocoder.com>
> > I think you have to reboot the 400.
>
> Thanks Bryan and Steve.
> I did an IPL and the console came up.
> Lesson that I learned:
> If you remove the console cable and plug it back in
> you must IPL. This is terrible.
>
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>