MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » April 2013

Re: Applying PTFs *PERM prior to new Cumulative/Groups



fixed

Ah, Pete....

I went ahead with it as DELAY(*NO) before your post came through.

It took 33 minutes and resulted in these messages:

Delayed PTF 5761SS1-SI34991 not permanently applied.

Delayed PTF 5761SS1-SI35237 not permanently applied.

Delayed PTF 5761SS1-SI37345 not permanently applied.

Delayed PTF 5761SS1-SI38286 not permanently applied.

Delayed PTF 5761SS1-SI40614 not permanently applied.

Delayed PTF 5761SS1-SI43419 not permanently applied.

Delayed PTF 5761SS1-SI43741 not permanently applied.

Delayed PTF 5761SS1-SI44133 not permanently applied.

Delayed PTF 5761SS1-SI45208 not permanently applied.

Delayed PTF 5761SS1-SI45453 not permanently applied.

Delayed PTF 5761SS1-SI45479 not permanently applied.

Delayed PTF 5761SS1-SI46281 not permanently applied.

Delayed PTF 5761SS1-SI46371 not permanently applied.

Delayed PTF 5761SS1-SI47135 not permanently applied.

Delayed PTF 5761SS1-SI47216 not permanently applied.

Delayed PTF 5761SS1-SI47322 not permanently applied.

PTF SI42485 not applied permanently.PTF SI38286 required.

PTF SI47136 not applied permanently.PTF SI47135 required.

PTF SI47136 not applied permanently.PTF SI47216 required.

PTF SI47269 not applied permanently.PTF SI47135 required.

PTF SI47296 not applied permanently.PTF SI47322 required.

Delayed PTF 5761SS1-SI34991 not permanently applied.

Delayed PTF 5761SS1-SI35237 not permanently applied.

Delayed PTF 5761SS1-SI37345 not permanently applied.

Delayed PTF 5761SS1-SI38286 not permanently applied.

Delayed PTF 5761SS1-SI40614 not permanently applied.

Delayed PTF 5761SS1-SI43419 not permanently applied.

Delayed PTF 5761SS1-SI43741 not permanently applied.

Delayed PTF 5761SS1-SI44133 not permanently applied.

Delayed PTF 5761SS1-SI45208 not permanently applied.

Delayed PTF 5761SS1-SI45453 not permanently applied.

Delayed PTF 5761SS1-SI45479 not permanently applied.

Delayed PTF 5761SS1-SI46281 not permanently applied.

Delayed PTF 5761SS1-SI46371 not permanently applied.

Delayed PTF 5761SS1-SI47135 not permanently applied.

Delayed PTF 5761SS1-SI47216 not permanently applied.

Delayed PTF 5761SS1-SI47322 not permanently applied.

Am I screwed for installing the Cumulative/Group PTFs this weekend since I only get the one IPL window?




"Contrariwise, if it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic."--Tweedledee
On 04/19/2013 11:25 AM, Pete Massiello - ML wrote:
No, you should either use DELAY(*YES) or my preference is DELAY(*IMMDLY). I don't use DELAY(*NO) because then some PTFs might not be able to be put on right now. With *IMMDLY, you get the best of both worlds. Those than can be done now are applied perm, and then those that can't are done at IPL, but you have redcued your IPL window by getting the ones you can on 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 Robert Clay
Sent: Friday, April 19, 2013 10:35 AM
To: midrange-l@xxxxxxxxxxxx; midrange-l@xxxxxxxxxxxx
Subject: Re: Applying PTFs *PERM prior to new Cumulative/Groups

Thanks for the info, Rob.

We have no Domino and really, just basic LPPs. We don't even have BRMS. No test PTFs at all.

So, will command

APYPTF LICPGM(*ALL) APY(*PERM) DELAYED(*NO)

be sufficient? Will it impact performance (this is our main production LPAR). Any idea how long it will take?

"Contrariwise, if it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic."--Tweedledee








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