Re: V7R3 DSLO combined image questions

I'd go about the same maybe a bit bigger

Jim Oberholtzer
Agile Technology Architects
Office: 414-433-4363
Cell: 414-915-1445
Sent from iPad

"I've learned that courage is not the absence of fear, but the triumph over it. The brave man is not he who does not feel afraid, but he who conquers that fear". -- Nelson Mandela

On Jan 9, 2018, at 2:09 PM, Steinmetz, Paul <PSteinmetz@xxxxxxxxxx> wrote:

Forgot to ask, one more item.

I'm calling the combined image I_BASE_01, which it needs to be if doing an install.
What should I set the image size to for V7R3?
My V7R1 image was around 20gb.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
Sent: Tuesday, January 09, 2018 11:12 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: V7R3 DSLO combined image questions

Nice!

1) Good idea, all the PTFs will be there when you create the image with LICPGM option 40.

2) Your call, if you're happy with the PTF load permanently apply them to
save space, (and time) but not required. IBM "Gold Copies" include temp
PTFs.

3) Yep. Assuming the same system, good idea. However have a CL program
ready to apply the keys anyway. The license key file method is also excellent, however I always go to my own file and use that to apply the keys as opposed to the IBM supplied file.

4) Good idea however you might find some of the duplicates and other objects don't restore quite like you would expect them to, so have a CL that sets all that up for you. It'll properly document the environment for you in addition to making corrections after installation easy.

5) There's no difference between the two. If you want create your own
profile to work as you would prefer. I'm normally using Install new system, which by the way has the same defaults as the other two.


--
Jim Oberholtzer
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Tuesday, January 09, 2018 9:33 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: V7R3 DSLO combined image questions

To the DSLO image experts.

I'm creating a DSLO combined image for my production V7R3 upgrades.
I have a V7R3 LPAR, most LPP, latest cum and all groups applied.
Minus save before and after, OS upgrade will be down to 1/2 hour.

1) Before creating the image, I'd like to ensure I'm not missing any critical PTFs not on a CUM and/or group.

2) Should the PTFs be perm applied before creating the image, or doesn't it matter?

3) Also like to ensure the license keys are part of the image so they don't have to be applied after the upgrade.
I was given these instructions from IBM years back, but the license keys were not restored.


DSPLICKEY PRDID(*ALL) LICTRM(*ALL) FEATURE(*ALL) SERIAL(*ALL)
OUTPUT(*LICKEYFILE) LICKEYFILE(QSYS/QALZALPKEY) LICKEYMBR(QALZALPKEY)



Preparing software license information for central site distribution

https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_71/rzai4/rzai4prepl
icinfo.htm


4) I'm also including all IBM cmd default changes, print file changes, etc.
This saves hours after the upgrade.

5) Is DSLO profile QRPLRELLVL a better choice than QIBMRPLRLS?.
My last upgrade I used QIBMRPLRLS, had some issues with some LPP not being updated from the DSLO image.

Any other DSLO suggestions will 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<mailto: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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD

--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD