MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » March 2014

RE: V6R1 to V7R1 i5/OS upgrade questions



fixed

Rob,

Reviewing my logs, test looks good, all LLP restored and all PTF loaded/applied from the image.
INZSYS did not occur until after I IPL'd.
Not finding my INZBRM, this was supposed to be auto submitted.

CPC3D86 Licensed program installation process completed successfully.
CPC3DDB Automatic installation completed successfully.

CPI3D81 Initialize System (INZSYS) started.
CPC37A9 Initialize System (INZSYS) processing completed successfully.

Paul

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, March 21, 2014 3:01 PM
To: Midrange Systems Technical Discussion
Subject: RE: V6R1 to V7R1 i5/OS upgrade questions

Paul,

When upgrading to the same release you should follow the instructions "Replacing Licensed Internal Code and IBM i of the same version and release" at http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/rzahc/upgradesameversion.htm
This was initially created for people upgrading from V5R4M0 to V5R4M5 or
6.1.0 to 6.1.1. It could also be applicable to those upgrading from beta code to current code. Or those upgrading from one resave to another (if you just really wanted to do it this way).

The steps there are suggesting a 'Manual' IPL and whatnot.
I did notice those steps leave out any LPP's. Which, if your goal is to get all PTF's is not going to make you happy if you're missing a PTF for
5770ST1 for example.
There's a possible check - DSPPTF 5770ST1.


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: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 03/21/2014 02:39 PM
Subject: RE: V6R1 to V7R1 i5/OS upgrade questions
Sent by: midrange-l-bounces@xxxxxxxxxxxx



I just tested automatic V7R1 upgrade using my latest V7R1 combined PTF
DSLO image to a hosted partition that already contains V7R1.
Was this a valid test to confirm an image?
PWRDWNSYS DELAY(60) RESTART(*YES) IPLSRC(*IMGCLG) IMGCLG(V7R1OSPTF)

Paul

-----Original Message-----
From: Steinmetz, Paul
Sent: Thursday, March 20, 2014 9:45 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: V6R1 to V7R1 i5/OS upgrade questions

Same machine, different LPARS.
If *no, will the V7R1 OS upgrade/install stop and ask for agreements to be
accepted.
If *yes, am I assuming they will be accepted as part of the image.

I also just discovered that you can include the license keys as part of
the image.
It must be named QSYS/QALZALPKEY
DSPLICKEY PRDID(*ALL) LICTRM(*ALL) FEATURE(*ALL) SERIAL(*ALL)
OUTPUT(*LICK
EYFILE) LICKEYFILE(QSYS/QALZALPKEY) LICKEYMBR(QALZALPKEY)
Output file QALZALPKEY created in library QSYS.
Member QALZALPKEY added to output file QALZALPKEY in library QSYS.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DrFranken
Sent: Thursday, March 20, 2014 9:31 AM
To: Midrange Systems Technical Discussion
Subject: Re: V6R1 to V7R1 i5/OS upgrade questions

I always think of it this way:

If the media is being used on the same machine as it's being created on
then I choose no. Technically I've already done that for that machine.

If it's going somewhere else, then yes. Oddly this is usually then done by
me but I always ask the customer "Do you accept the IBM License terms so I
can accept the agreements?" Never had anyone say "No." But then usually
they say something like "We'll have to accept the agreements in order to
see what's in them!" :-)

- Larry "DrFranken" Bolhuis

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

On 3/20/2014 8:45 AM, Steinmetz, Paul wrote:

Another DSLO question.
When building the DSLO image, License Acceptance Required, should this
be *yes or *no?

Paul

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, March 20, 2014 8:24 AM
To: Midrange Systems Technical Discussion
Subject: RE: V6R1 to V7R1 i5/OS upgrade questions

After some special work yesterday, and a rereading of the manuals, I
believe that you're right, the INZSYS should kick off after the PTF IPL.
They even say something like "if you're some sort of freaking idiot and
are not going to put on any cume after upgrading your OS then start the
INZSYS, otherwise it will automatically start upon the IPL from the cume".
Well, I suppose people like Pete and Larry who upgrade from custom
media with all the latest PTF's on it, might be the exception.



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: Pete Massiello - ML <pmassiello-ml@xxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 03/19/2014 11:33 PM
Subject: RE: V6R1 to V7R1 i5/OS upgrade questions
Sent by: midrange-l-bounces@xxxxxxxxxxxx



I do it all the time. Let me give you an example. I have special
PTFs to apply before applying the latest cumulative, so I do a CHGIPLA
start back in restricted, load the special PTFs, and then IPL. Now, I
let the system load all the new PTFs, and IPL. Perfect example.

I always apply my PTFs first before doing the IPL which kicks off
INZSYS.

Pete

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





-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, March 19, 2014 7:27 AM
To: Midrange Systems Technical Discussion
Subject: RE: V6R1 to V7R1 i5/OS upgrade questions

I do not think that CHGIPLA to bring the system up restricted during
an upgrade is recommended. When do you have it fire off the INZSYS?
After the cume IPL?


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: Pete Massiello - ML <pmassiello-ml@xxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 03/18/2014 11:11 PM
Subject: RE: V6R1 to V7R1 i5/OS upgrade questions
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Jobs remain in the job scheduler between OS releases.

Perhaps the best way is to do a CHGIPLA, and start the system up
restricted. This way you only have the console up and you can do what
you need after the upgrade (Like Apply PTFs, or do a full backup before
returning the system to the users). I wrote an article last month in
my

System admin Tips and Techniques newsletter on just this:
http://www.itechsol.com/newsletters/2014-02.html

Pete

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





-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Tuesday, March 18, 2014 2:57 PM
To: 'Midrange Systems Technical Discussion'
Subject: V6R1 to V7R1 i5/OS upgrade questions

1) Can future scheduled jobs remain in the jobq across a V6R1 to V7R1
i5/OS upgrade?
2) Is the simplest way to prevent AJS (Advanced Job Scheduler) jobs
from running during or after the upgrade is to hold or end the AJS
monitor as opposed to holding or omitting next run of individual jobs?

Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx
http://www.pencor.com/

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