Re: Thin client was: MIDRANGE-L Digest, Vol 12, Issue 1922

Regarding Operations Console ("OC") and LAN Console ("LC"):

I used to have OC as I was one of those who believed the console should
have it's own "special wire." When it got to the point that OC was no
longer going to be supported, I was forced to go to LC.

I followed some advice from here (forget if it was Pete or Larry). I
actually put a 2nd ethernet card in each of 2 PCs here, used an old Linksys
switch, and I have LC available on 2 PCs on an entirely separate network,
so to speak. I had some issues which IBM software support resolved in
pretty short order. And LC is way way better than OC. Much quicker to
respond. And the console is definitely there even in restricted state. I
VPN in from home to my desktop at night while watching TV and do IPLs when
necessary to apply PTFs.




On Thu, Oct 3, 2013 at 7:35 AM, <rob@xxxxxxxxx> wrote:

Okay speed readers, slow down and read the posts. :-)

"Thin client" is NOT a generic term. It is a term for a very specific
piece of, ahem, hardware. It was only useful on a few select platforms.
Anything boldly labeled a Power system will not use them. I don't count a
Power 5 as boldly labeled a Power system as IBM still marketed those as
system i or whatever. A thin client will NOT work on a Power 6 or a Power
7.

The only system consoles available on a Power 7 are:
- Lan console. Great for single partition machines.
- HMC or Hardware Management Console. Darn near required for multiple
partition machines, with a few exceptions.
- FSM or Flex Systems Manager. I've no experience with this. The name
seems to indicate it's for IBM "Flex" systems.

I've used the first two. Once back on a Power 4 multilpar machine. And
once on a side job with a single lpar machine. Actually the Power 4 setup
was Operations Console and not Lan Console.

Buzz, your LAN console connection is what you want to use. You can start
up a 5250 console session on it and it should default to running in your
controlling subsystem. This session should continue to run even in
restricted state. Yes, it does amaze me how IBM can get just enough low
level TCP running to support Lan Console and not restrict a rclstg, full
system save, etc, not one whit. You can do an ENDTCP and a ENDSBS *ALL
*IMMED and your console will not be affected. It can do your PWRDWNSYS
and you will see the screen as it apply ptf's and everything else. You
can use your favorite PC Anywhere or Dameware software to take control of
this remotely.

The difference between Operations Console and Lan Console was that your
Lan Console was on your Lan. And you could have more than one (as a
backup or whatever). Operations Console required a special wire. Yes,
there are those who feel it doesn't count as a system console if it
doesn't have it's own unique wiring system.
Operations Console has been discontinued.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Buzz Fenner" <bfenner@xxxxxxxxxxxxxxxx>
To: <midrange-l@xxxxxxxxxxxx>,
Date: 10/02/2013 03:48 PM
Subject: RE: MIDRANGE-L Digest, Vol 12, Issue 1922
Sent by: midrange-l-bounces@xxxxxxxxxxxx



On Wed, 2 Oct 2013 09:52:01, Rob Berendt wrote:

Sorry but there's some miscommunication here.
I want to know the model number of your thin console, not your power 7
machine.

Rob,

Sorry about the mix up, we don't have a thin console connection but use a
LAN connection. But I did check in the hardware information center and
found
this:

"Use the Thin Console on the following models: 9405-520, 9406-520,
9406-525,
9406-550, and 9407-515. These models must be running i5/OS V5R3 or later
and
a firmware level or SF240 or later."

However, I really like the flexibility afforded with that sort of
connectivity; I'll even tunnel in from home and do system administration
tasks. Heck, even using Access Client Solutions on a Win 8 laptop (thanks
Tim!).

--
Buzz


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.