|
That might work. I tend to do this:
APYPTF LICPGM(*ALL)
APY(*PERM)
DELAYED(*YES)
Since the odds are likely that there will be some delayed PTF's anyway
why not just apply them all at IPL time with DELAYED(*YES)? That, and
your concerns about special instructions are greatly reduced. For
example "this is an immediate ptf but you do have to end all tcp and
start it up again". I've found that to be slightly disruptive to the users.
Now, the only time I do not use LICPGM(*ALL) is when there are vendor
applications which also use the PTF process and I do not want to
permanently apply them. For example, Domino. I routinely have to
RMVPTF any hot fixes applied to that before putting on an upgrade. So
I never want to perm apply those hotfixes.
Since I have Domino on a bulk of my lpars I have to break it down by
individual product more times than not.
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: Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx<mailto:jlcrosby@xxxxxxxxxxxxxxxx>>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxx>>
Date: 01/25/2017 02:57 PM
Subject: Permanently apply PTFs that are currently temporarily
applied
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx<mailto:midrange-l-bounces@xxxxxxxxxxxx>>
V7R1, haven't permanently applied PTFs in a while (though I have tons
of them temporarily applied), and I'm having a brain fart.
I'm fairly well up to date on PTFs and before I order the next cume, I
want to permanently apply all PTFs that are now temporarily applied.
Is this the proper way to do this:
APYPTF LICPGM(5770999)
APY(*PERM)
DELAYED(*IMMDLY)
for each product, then IPL?
Thanks.
--
Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com<http://www.dilgardfoods.com>
The opinions expressed are my own and not necessarily the opinion of
my company. Unless I say so.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto: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<mailto:MIDRANGE-L-request@xxxxxxxxxxxx> Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx<mailto: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<mailto: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<mailto:MIDRANGE-L-request@xxxxxxxxxxxx> Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.