Re: PTF apply philosophyies

Remember that IPL to "A" or "B" is a LIC only statement. That is an IPL from LIC Copy "A" only reverts LIC PTFs. PTFs for IBM i and the LPPs do not revert back to the perm applied version when the system is IPLed from the "A" side.

- Larry "DrFranken" Bolhuis

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

On 6/5/2014 7:56 PM, Roberto José Etcheverry Romero wrote:

I would wager that applying ALL PTFs before an installation makes it easier
to reverse the changes in a hurry, just hop to the A side and it'll be the
config you had just before, otherwise going to the A side would mean having
the LIC as you had it but all other LPP at who knows what point in time...


On Thu, Jun 5, 2014 at 7:41 PM, Bakutis, Becky <
BBakutis@xxxxxxxxxxxxxxxxxxxx> wrote:

"Generally I do like load and run Temp and SAVE 22. Run for perhaps 2 or
3 months. Then perm apply all and SAVE 22. Then repeat as necessary."

This brings up a question I have and am interested in what others do.
Currently immediately before applying a new CUME I apply the 5770999 PTFs
permanently. Someone asked if maybe we should apply all PTFs permanently
prior to applying a CUME. Is there a reason to apply all other than having
a base level of PTFs?


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
DrFranken
Sent: Thursday, June 05, 2014 5:05 AM
To: Midrange Systems Technical Discussion
Subject: Re: PTF apply philosophyies

I do a LOT of PTFs and spoken to many of the fine folks at IBM re PTFs and
the process.

First off it has been stated that MANY PTFs simply require an IPL. The
objects being replaced simply cannot be updated at any other time as they
are always in use or otherwise locked. A claim of 90% of PTFs can be
applied immediately doesn't align with what I see. I suppose it's possible
in fact but with all the pre and co requisite PTFs all it takes is one PTF
in the 'set' to require an IPL and the other PTFs are stuck so effectively
all the PTFs require an IPL.

I have heard several times that using *IMMDLY (Immediate if possible,
Delayed to IPL when mandatory) Is NOT recommended for any PTF Groups
including CUMEs. It's essentially impossible to read every cover letter and
deal with all the special instructions. Failure to follow the special
instructions can mean many things, not the least of which is that many of
the PTFs that APPEAR to be applied are not active until an action is taken,
frequently the action is to IPL (which I find annoying!)

I do concur with other comments that if you are not provided sufficient
time for backups, PTFs, and other maintenance then having an HA system is
near mandatory. Clearly NOT doing PTFs and proper saves is just a system
crash looking for a bad time to occur. If time is so short when you DO get
a window that any problems push you into being considered an outage that
also is 'living on the edge'. Also consider making your load source disk
an SSD, this will 'enhance PTF apply performance.'

Generally I do like load and run Temp and SAVE 22. Run for perhaps 2 or
3 months. Then perm apply all and SAVE 22. Then repeat as necessary.

- Larry "DrFranken" Bolhuis

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

On 6/4/2014 11:56 AM, Steinmetz, Paul wrote:

Management would like to minimize the IPL, PTF, and system save

downtimes.

HA/DR Is out of the question.
Currently, I try to IPL Production every 2 months for PTF apply along

with a system save.

The IPL and system save will probably go to 6 months or as needed.
90% of PTFs can be applied immediately without an IPL, however IBM does

not recommend immediate apply for more than a single PTF.

Applying a large amount of PTFs immediately has caused issues in the

past.

Permission has been granted for the PTF immediate apply, but I'm weary

from previous issues.

Any thoughts from the group.

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.