MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » January 2013

Re: What to expect with a 9406-170?



fixed

I have an old 170 in the lab that's only there for spare parts for
some clients. I still reload it sometimes (when i need to test and old
tape drive or the like) and the keys were lost to the times (i found
some keys but for another serial that we had scrapped d'oh). It works
like a charm.

Best Regards,


On Mon, Jan 21, 2013 at 9:14 AM, <rob@xxxxxxxxx> wrote:
You all know I eschew obsolete operating systems, but if you're running a
170 you're stuck there anyways. So, in that spirit, if you are going to
reload this machine you'd better keep keys in mind. If you do not have OS
(and lpp) keys for the version of OS you are planning to load you may be
better off loading V4R5. I don't think that V4 required keys.

Otherwise you have 70 days to play with it. And I thought that IBM put
something in there to know if you do something tricky; like try to reload
every 70 days to get around it.


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: DrFranken <midrange@xxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 01/20/2013 06:51 PM
Subject: Re: What to expect with a 9406-170?
Sent by: midrange-l-bounces@xxxxxxxxxxxx



9406-170 will run V5R3 happily so pretty much any V4 or V5 CD prior to
V5R4 is worth a try.

- Larry "DrFranken" Bolhuis

www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com

On 1/20/2013 6:38 PM, Roberto José Etcheverry Romero wrote:

Clay,

Best way to test the hardware is to put the panel in D M and IPL from
I_BASE_01 cd for a 170 i think v4r5 or maybe v5r1 is the highest OS
ver you can use. If the console hardware is OK you should get to the
DST from CD and check the disks with "initialize" if everything goes
OK you can then install a fresh copy.

Best Regards

On Sun, Jan 20, 2013 at 7:18 PM, Clay B Carley <cbc@xxxxxxxxx> wrote:
Hi Rob & list,

The cat 5 cable has been a cable I use on a daily basis, and tested
with
a Fluke after I didn't see anything on the terminal. The splitter is
the one that came with the 3476, however it's a refurbished unit that
didn't come with a manual at all. I was surprised it came with the
splitter & power cable! The 4-port brick is connected to the 9-pin
connector on the correct card according to the manual I found from IBM.
And, the twinax balun is plugged into port 0 on the brick.

I did some more testing today, and after some info from DrFranken,
looking at what the panel was telling me it seemed to indicate that
perhaps the drive in slot 1 had failed. Pulling that drive, I now get
a
new code with the attention light: B1014504, which attempting to decode
I found "load source failed or not found". Putting any disk in slot 1
causes the 675A3200 src to appear, but moving that drive to another
slot
does not cause that src to show up.

I'm guessing that the drives were zeroed out from the previous owner
(well, probably a couple of owners back anyway).

Again, I really appreciate everyones help!

Clay Carley


rob@xxxxxxxxx wrote:
It's been a decade or so since I've used twinax so I can't remember
much
about that crap, like if the cursor is in the top right does that mean
the
terminal is connected ok but the system isn't ready for it?
Obvious question: Is the brick connected to your 170?
Are you using the 0 port on the brick?
How was your Cat 5 test performed? Did you use the same pair of
baluns
and wire on another midrange product? Was the wire attached via RJ
jacks
or hard wired in? If hardwired, do you have the polarity right?

is the twinax splitter the one that came with the 3476? Ones
manufactured
for other models often are not interchangeable.

Couldn't quickly find a manual for the 3476 online.

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


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






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact