RE: Moving Operations Console from one computer to another

I would agree with everything that everyone has said so far, but using
Operations Lan Console 6.1/7.1 with OS 6.1/7.1 is so much better. It seems
to get around the QCONSOLE device issue by auto creating its own. This does
make connecting easier.

Pete

--
Pete Massiello
iTech Solutions
http://www.itechsol.com

Add iTech Solutions on Facebook:
http://www.facebook.com/group.php?gid=126431824120
Add iTech Solutions on LinkedIn: http://www.linkedin.com/groups?gid=2206093

iTech Solutions because IBM i (AS/400s) didn't come with System
Administrators


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jack Kingsley
Sent: Tuesday, June 14, 2011 8:14 AM
To: Midrange Systems Technical Discussion
Subject: Re: Moving Operations Console from one computer to another

Do you have it setup to take over the console?? What in FLIGHTLOG were you
changing. Be advised that this writes entries to your HOST table file on
your PC as well. The drawbacks that I don't like about lan console is that
there are no API's to get any of the ip settings in the event you need to
know what they are.

On Mon, Jun 13, 2011 at 5:58 PM, Tom Hightower <tomh@xxxxxxxxxxx> wrote:

Operations Console, with the PC directed-connected to the T1 ethernet
connection on the back of the iSeries. He kept referring to it as Ops
Console, but I reckon that would be LAN console. I asked if I couldn't
just
reset the password as you suggest, but he had me walk on thru and adjust
something in "FLIGHTLOG" (which I'd never heard of). I just wish I'd had
time to write down what he had me change, and the value to set it to.

TomH

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Kirk Goins
Sent: Friday, June 10, 2011 7:48 PM
To: Midrange Systems Technical Discussion
Subject: Re: Moving Operations Console from one computer to another

If you are talking OPS Console, I don;t think there is much if anything.

If

you are talking LAN Console then there is some work.

When LAN Console first connects some VooDoo magic happens between the
system
and the PC. The system knows soem specific information about that PC and
that connection. If you delete and rebuild that connection or try to use
another PC with the same conection setup it won't work.

If you are using the connection device of QCONSOLE then go into Work with
service tools user IDs and Devices Service tools device IDs and then use
2=Reset password for the device name yo are connecting to.
You should then be able to connect that new PC.

On Fri, Jun 10, 2011 at 3:36 PM, Tom Hightower <tomh@xxxxxxxxxxx> wrote:

When originally setting our new v6r1 system, I configured my laptop as
the Ops Console. Since then we've received a new PC to be used as the
Ops Console (instead of my laptop). Our VAR says I need to do
something before I start using the new PC as the Ops Console (other
than installing the Client Access software) - what would that be?


TomH

--
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.

--
Kirk
--
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.