RE: The joy of ops console = no joy...

Charly,

Here's some thoughts, no definite answer.

The IP address should be irrelevant.  At V4R4 (or thereabouts) you're
only looking at a serial connection.  If you're tinkering with the PC's
network configuration, you're looking in the wrong area.

If it is truly a V4R4 box, you may have better luck with an older
version of Client Access.  At the time V4R4 shipped, Client Access
Express for Windows 95/NT was the product.  I'm guessing here because I
don't know how backlevel you can push the console functions, using the
latest and greatest without a corresponding microcode update may not
work.

If you are at V4R4, you should have a #2721 Communications IO Adapter.
Make sure that you are attached to the correct port.

I regret I don't know the SRC codes off the top of my head.

HTH,
Andy Nolen-Parkhouse

> I am still trying to make this ops console thing work...
>
> A model 150 - with an unknown operating system.  It _might_ be at
V4R4,
> but
> I don't really know.  It might have been as long ago as 1999 that this
> system was functioning.  I _think_ I know the IP address of the ops
> console.
>   It did work at one time.  With an ops console.  Then stopped
working.  I
> _think_ I know an all-powerful profile and password that is not
QSECOFR.
> The ops console cable is part number 97H7557.  I have tried V5R1 CA
> Express
> on the console (with and without the "iSeries Ops Console Update"
> SK3t-4114-01).  No joy...  I have read all the "setup guides" and run
> various flavors of "EZ" setup.  No joy...
>
> I have seen various messages that I interpret as "no console"
messages.
> Like A600 5001.  I have tried a D M ipl to reload the operating
system.
> No
> joy...
>
> Most recently I got an SRC that I have never seen before - 0000 2222.
>
> Anyone know what 0000 2222 might mean?  And does anyone have any
> suggestions
> on the best way to proceed?  Other than buy a new 270?
>
> Thanks a bunch,
>
> -- Charly