I'd suggest that, instead of Ops Console, you use Lan Console. That way you can define 1-n workstations to be a console (though only one can actually be at a time, of course). If the PC that is currently the console goes dead, it's a piece of cake for another PC, which has been defined as Lan Console capable, to take over the session without a hiccup. Been there, done that.
Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Monday, March 22, 2010 4:58 PM
To: Midrange Systems Technical Discussion
Subject: Re: Installing a 520 for the first time
James Rich wrote:
Am I correct that I just need to install Ops Console on any windows
machine?
Yes, and get it patched into the console Ethernet port (which is
separate from the general use Ethernet port).
As I recall, when a WinDoze box with Ops Console looking for something
to connect to at a specified IP address, and a console Ethernet port
looking for an Ops Console (but not knowing its own IP address, much
less the console's) are brought together on the same LAN, they will
automagically find each other.
I think if you check the MIDRANGE-L archives for a few months ago (try
for mid-December), you'll find a thread in which List members were
talking me through the very process that's ahead of you.
--
JHHL
midrange.com
