RE: I5 systems in production -- MIDRANGE-L

I've seen 3 main problems with Ops Console

1. Running it on Win 2K SP4 - there is a known problem with this. There is a link at www.iseries.ibm.com/access that points to MS. Unfortunately, you need to convince MS you really have the problem, I hear. Larry Bolhuis, on this list, got it and sent it on to me when I asked him to. I regret that I lost it - forgot to copy it off the machine at my previous job. Maybe find his email on this list's archive and see if he still has it.

2. IP subnetting conflict - Ops Console direct connect insists on a certain subnet - 192.168.0.1 - .255, I think. If this is also your company's internal subnet, Ops Console will not work. Either use a laptop or other machine not connected to your network, or change your network's entire addressing scheme. ;-)

3. Disconnecting the direct connect cable can cause a loss of connection that I used to think only an IPL could fix. But another post gives a procedure for this.

Once these were resolved, Ops Console worked really well for me.

HTH
Vern

At 11:54 AM 11/24/2004, you wrote:

> We've had nothing but problems with pc ops console.  It's
> been inoperative for about a month now, were looking to
> schedule some downtime so we can re-ipl.  That's the only
> thing we've found that will bring it back.

I have Big Plans for the pc ops console slightly down the road.

--
Jeff Crosby
Dilgard Frozen Foods, Inc.
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531

The opinions expressed are my own and not necessarily the opinion of my
company.  Unless I say so.

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