MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » April 2014

RE: V6R1 to V7R1 i5/OS DSLO image upgrade issues



fixed

Here's my latest brainstorm.
I'm going to include all customization in my DSLO image, this will save 1 to 2 hours of down time after the upgrade.
Cmd defaults, print file changes.
I'm also going to include TAATOOLs in my DSLO image.

Hope to test this all next week.

Minus save before and after, I have the OS upgrade down to 1/2 hour.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DrFranken
Sent: Wednesday, April 02, 2014 4:53 PM
To: Midrange Systems Technical Discussion
Subject: Re: V6R1 to V7R1 i5/OS DSLO image upgrade issues

Works great too, especially when the partition that is hosting the image is not capable of automatically swapping volumes during an update. This includes VIOS and IBM i 6.1 as a host. Now with one image you get it all. My image gets to about 15GB for a full install with PTFs.

- Larry "DrFranken" Bolhuis

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

On 4/2/2014 4:49 PM, Steinmetz, Paul wrote:
Update from IBM.
okay to support up to 1tb on virtual optical image Only need one image
for a combined OS/CUM/PTF DSLO image.

Paul

-----Original Message-----
From: Steinmetz, Paul
Sent: Thursday, March 27, 2014 9:22 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: V6R1 to V7R1 i5/OS DSLO image upgrade issues

Pete / Larry,

Sorry, should have stated this clearer.

I saw an disk savings 2% or 58 gb.
My V7R1 LPAR is smaller than my V6R1 LPAR

Paul

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DrFranken
Sent: Thursday, March 27, 2014 8:54 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: V6R1 to V7R1 i5/OS DSLO image upgrade issues

Agreed. I've never seen even 10G with a complete set of LPPs on the
system. On our iDevCloud system we have several IBM i 7.1 partitions
with only 51 GB of total disk! :-)

- Larry "DrFranken" Bolhuis

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

On 3/27/2014 7:20 AM, Pete Massiello - ML wrote:
Paul,

I have not seen such a large increase at all. I see maybe 3 to 5GB, not 58. You have either left the images on the new machine, or something else is on the machine now.

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: Wednesday, March 26, 2014 1:21 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: V6R1 to V7R1 i5/OS DSLO image upgrade issues

One added note, which I thought was strange.,
V6R1 to V7R1 upgrade resulted in a gain of 2% or 58 gb.
I would have thought the opposite.

-----Original Message-----
From: Steinmetz, Paul
Sent: Tuesday, March 25, 2014 2:32 PM
To: 'Midrange Systems Technical Discussion'
Subject: V6R1 to V7R1 i5/OS DSLO image upgrade issues

For confirmation and for the archives, I have some DSLO image questions that hopefully will make the next i5/os upgrade better/smoother/faster.
In addition to the dedicated save before and save after, V7R1 OS upgrade was only 30 minutes, customization afterwards, 1 1/2 hours.

1) I used installation profile QIBMRPLRLS. This was fine except for iSeries Access 5770XE1, target was already at V7R1, but not latest SL, SI49800.
The source LPAR that built the image was at SI50567 Permanently applied.
Using installation profile QRPLRELLVL instead would have been a better choice, 5770XE1 would have been updated with the latest SL from the DSLO image.

2) I was missing a LLP product as part of my image, I didn't realize until after the upgrade. Is it correct that if do a 11=Work with object links on the image catalog, you should see an entry for each LPP you intend to upgrade. If you don't see one, then that LPP is not part of the image and will not be upgraded.
Q5770BR1 DDIR
Q5770DE1 DDIR
Etc.

3) If you have any i5/os customization, I could have applied that customization to the source LPAR that built the image, thus after upgrade, you would not have to do the customization, customization restored as part of the image. This will shorten the down window. Some IBM commands are always customized and we change some defaults on all IBM printfiles.
TAATOOLs must be upgraded with each i5/os. Because TAATOOLS is release dependent, you can't install the new version ahead of time. However, I could have included TAATOOLS as part of the DSLO image, but then would need a user-defined installation program. Has anyone ever done this?

4) I included my lic keys at part of the image, however, they were not restored, not sure why at this point?
DSPLICKEY PRDID(*ALL) LICTRM(*ALL) FEATURE(*ALL) SERIAL(*ALL)
OUTPUT(*LICK
EYFILE) LICKEYFILE(QSYS/QALZALPKEY) LICKEYMBR(QALZALPKEY)

Any other DSLO image tips, etc, would be deeply appreciated.

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