Re: V5R4 upgrade

Hardware vs. Software. I remembered lack of support, but neglected to
remember it was at hardware level. At the time I was reading that, the
concept of upgrading the operating system appeared to be non-existent.
Like everything else in life, appearances are subject to change. No
hardware changes. First thing I saw in MTU was infor on changing console -
which would not appear to be an issue.

Boss is willing to skip upgrade and just ride out no software support.
Made it my call, subject to final approval of regional manager. Gets very
confusing.

Why do the upgrade? If relevant, see below:

Biggest reason to go with the upgrade, beyond software maintenance, is for
me to have a place in the new organizational structure. Since transition
to centralized system, I have had very little to do. I am hoping to remain
useful. The LAN console replacement came out of the blue. I wish I had
had the time to be better prepared. Almost no access to the system and I
got very rusty. Happens quickly. Too "young" yet to "retire".

Yet another dumb question (even to me) is how are processors identified as
to which POWER family? We definitely are not POWER7. From description
above, it would appear to be POWER5.

I did two OS upgrades on a CISC box a long time ago. No Internet, so had
to read and hope I had it right. Place was NOT friendly. Boss demanded
many updates. He wanted more than just that upgrade was working.

Thanks for the understanding and assistance. It is much appreciated.

John McKee


On Wed, May 15, 2013 at 12:09 AM, Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>wrote:

John,

As Evan stated earlier, V7R1 should support twinax, but Power7 will not.

Supported console options for IBM i 7.1
On POWER5 or POWER6 systems, supported console interfaces include the
following options:
Operations Console LAN attached
Twinax console (which is IOP-based)
HMC managed console
POWER6 does not support any IOPs in the central processor complex.
Therefore, any
IOP-based interface, such as Twinax, must be placed in an HSL attached IO
drawer and an
HMC is required to tag the console location.

Support: Operations Console Direct attached and Twinax console are not
supported on
any POWER7 processor-based server. IBM i console options on POWER7 consist
of
either Operations Console LAN attached or HMC managed console

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John McKee
Sent: Tuesday, May 14, 2013 6:47 PM
To: Midrange Systems Technical Discussion
Subject: Re: V5R4 upgrade

Thank you for the clarification as to supported hardware. I tried several
searches but got it wrong.

Comments about vendor supported software is already on my list. Been
through that with move to v4r2 a long time ago. A lot fewer vendors are
involved now. We were behind on operating system back then. All vendors
had moved on. Might be the same issue now, considering the gray hair on
v5r4 - but, as Rob has related, vendors do drag feet.

John McKee


On Tue, May 14, 2013 at 5:08 PM, Evan Harris <auctionitis@xxxxxxxxx>
wrote:

Twinax going away relates to hardware changes on later Power models.
You won't lose twinax connectivity simply as a result of the upgrade.

You need to establish specifically that all your vendors software is
supported V7R1. Finding out afterwards there is an issue would not be
a good situation.




On Wed, May 15, 2013 at 9:44 AM, John McKee <jmmckee@xxxxxxxxxxxxxx>
wrote:

Helpful idea. The stuff that didn't pass ANZOBJCVN at least had
very old version info.

Chatted with boss. His concern is whether vendor software works at

7.1.

I

see no reason it wouldn't. But, won't hurt to check.

We do have a 6262-T22 Line printer with twinax interface. I know I
read

on

some post that something went away on 7.1 I have not found Rob's
post about it yet. That WOULD be a show stopper for 7.1. If I
could only recall what Rob referred to - makes searching easier for

one thing.

John McKee


On Tue, May 14, 2013 at 2:36 PM, Eric Lehti
<elehti@xxxxxxxxxxxxxxxxxx

wrote:

Object conversion sets use count and Last-used date to zero.

I recommend that before you do the object conversion that you
DSPOBJD *FULL all your libraries where you store software and
data. That will preserve for you the *USE count info that you
like. Last-Used is handy to keep a record of.

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

--

Regards
Evan Harris
--
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.