Re: Perm vs Temp PTF applies

wrote:

Hopefully you're current on cumes and groups.

just the cumes .. what groups do you recommend?

On Thu, Apr 12, 2018 at 9:10 AM, Jack Woehr <jwoehr@absolute-performance.
com> wrote:

Thanks, Paul and Rob ...

One thing I'm confused about ... does

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

apply PTF's I have downloaded but not yet applied even temporarily?

On Thu, Apr 12, 2018 at 9:07 AM, Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
wrote:

From what I remember from my experiences, if the PTF required an IPL to
originally install, then it also required an IPL when going from Temp to
Perm.

My first attempt was:

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

There are about 20 SI PTFS, that remained temporarily applied, requiring
an IPL to perm apply.

CPF3994 Information 10 02/21/18 16:44:54.168533
QPZAPC QSYS 1653 QUIMNDRV QSYS 0607
Message . . . . : Delayed PTF
5770SS1-SI62053 not permanently applied.
Cause . . . . . : The requested
PTF is a delayed PTF and cannot be
permanently applied using the
DELAYED (*NO) parameter of the Apply PTF
(APYPTF) command. Recovery . . .
: Delayed PTFs can only be applied when
the system is initially started
(at IPL).

2nd attempt.
APYPTF LICPGM(*ALL) APY(*PERM) DELAYED(*IMMDLY)
IPL

Message ID . . . . . . : CPF35CA
Date sent . . . . . . : 02/25/18 Time sent . . . . . . :
02:41:02

Message . . . . : PTFs applied or removed during IPL.

Cause . . . . . : The PTFs that were identified to be applied or
removed
during this IPL were applied or removed successfully.

UPDPTFINF
DLTPTF PTF(*PRMAPY) LICPGM(*ALL) -( removes savf and cover letters from
QAPZCOVER.


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Jack Woehr
Sent: Thursday, April 12, 2018 10:51 AM
To: Midrange Systems Technical Discussion
Subject: Re: Perm vs Temp PTF applies

I'm just shooting to do this migration this weekend.

My thoughts are:

- Apply PTFs perm
- update ptf info and delete ptf
- SAV 21

etc.

On Thu, Apr 12, 2018 at 8:46 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

I think it was Larry or Jim who put steps in that thread which
involved an extra save or two. I'd check the archives. I don't quite
go to that level.


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: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx

Date: 04/12/2018 10:38 AM
Subject: Re: Perm vs Temp PTF applies
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Paul Steinmetz wrote last month:

APYPTF LICPGM(*ALL) APY(*PERM) DELAYED(*IMMDLY) UPDPTFINF DLTPTF
PTF(*PRMAPY) LICPGM(*ALL) -( removes savf and cover letters from
QAPZCOVER.

Is there an IPL in there?
Should one do a full system save before? Is this dangerous in any way

if

the system has been running on the temporarily applied PTFs for some

time?

On Fri, Mar 16, 2018 at 6:56 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

<snip>
Did you run UPDPTFINF before you ran DLTPTF?
I found this made a difference.
Additional savf were found and deleted.
</snip>

I believe so

<snip>
APYPTF LICPGM(*ALL) APY(*PERM) DELAYED(*IMMDLY)
UPDPTFINF
DLTPTF PTF(*PRMAPY) LICPGM(*ALL)
287 PTFs deleted.
</snip>

UPDPTFINF, according to the help, only updates from the save files in
QGPL. Not QPTFOBJ1 or other libraries you may have stored ptf save

files

into.

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: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 03/16/2018 08:51 AM
Subject: RE: Perm vs Temp PTF applies
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Rob,

Did you run UPDPTFINF before you ran DLTPTF?
I found this made a difference.
Additional savf were found and deleted.

Even after running UPDPTFINF followed by DLTPTF, I still had savf

that

had

to be manually deleted.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf

Of

Rob

Berendt
Sent: Friday, March 16, 2018 8:21 AM
To: Midrange Systems Technical Discussion
Subject: RE: Perm vs Temp PTF applies

Just ran the following on one a sandbox lpar which has been around

for a

long time.

APYPTF LICPGM(*ALL) APY(*PERM) DELAYED(*IMMDLY) UPDPTFINF DLTPTF
PTF(*PRMAPY) LICPGM(*ALL)
287 PTFs deleted.

This system does not have PDM so I ran
wrklnk '/qsys.lib/qgpl.lib/qapzcover.file/*'
Then I used 5 to view them. These are for some products not on my

system

(at least not anymore). For example 5733-ARE. Which explains this

dspptf

5733are Product 5733ARE *ALL not supported or installed.

So, apparently these members I will have to remove manually.
DLTPTF, with the *PRMAPY option, will not delete cover letter only

PTF's.

Like SF98730.
DLTPTF PTF(*COVERONLY) LICPGM(*ALL)
PTF 5770SS1-SF98730 V7R3M0 deleted.
1 PTFs deleted.

Now I'm down to:
DSPFD FILE(QGPL/QAPZCOVER)
Total number of members . . . . . . . . . : 131

DLTPTF PTF(*SAVFONLY) LICPGM(*ALL)
126 PTFs deleted.

Now I'm down to:
DSPFD FILE(QGPL/QAPZCOVER)
Total number of members . . . . . . . . . : 5
And their save file are still on my system All of these are for

products

not on my system.

DLTPTF PTF(*ONORDONLY) LICPGM(*ALL)
No PTFs found.

I ran
DLTPTF PTF(...)
For these remaining 5
Now QGPL/QAPZCOVER has no members.

I used an SQL service to scan my system for all save files.
I found several in QPTFOBJ1.
These are all
PTF status . . . . . . . . . . . . . . : Permanently applied
Unattended IPL action . . . . . . . . : None
Action pending . . . . . . . . . . . . : No
Action required . . . . . . . . . . . : No
Temporarily applied date/time . . . . : 03/05/18 10:57:13

Why would these save files still be here?
Perhaps I once ran DLTPTF and some were only temp applied? Would

have

had

to been somewhat recent.


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: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 03/05/2018 02:38 PM
Subject: RE: Perm vs Temp PTF applies
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



From my recent discovery, here's the sequence.

APYPTF LICPGM(*ALL) APY(*PERM) DELAYED(*IMMDLY)
UPDPTFINF
DLTPTF PTF(*PRMAPY) LICPGM(*ALL) -( removes savf and cover letters

from

QAPZCOVER.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf

Of

DrFranken
Sent: Monday, March 05, 2018 12:01 PM
To: Midrange Systems Technical Discussion
Subject: Re: Perm vs Temp PTF applies

So this temp vs perm thing. Much FUD and such here.

First you cannot NOT apply PTFs perm, it's just not possible. Jim and
others have already pointed this out. In MANY cases (ALL?) where

there

is

a PTF being temp applied that supersedes the previous PTF that

previous

PTF is Perm applied. In addition all PTFs that the old PTF has as a
pre-req or co-req are also permanently applied. So this happens for

this

reason all the time.

Then there is the Technology Refresh. Basically when you apply the
enabling LIC PTFs for a TR which are the MF99xnn PTFs, (here nn is

the

TR

number and x is 0 for i 7.1, 1, for i 7.2 and 2 for i 7.3) the system

will

perm apply all the PTFs in the LIC. This is because basically that
MM99 guy will supersede pretty much the entire LIC. So that happens

too.

Then there is the disk space that has been talked about. Temp applied

PTFs

consume space. Now I sell disk space so use all you want but if you

don't

want to waste it, do some perm applies.

Then as Steve mentioned if the difference between the A LIC and the B

LIC

are so vast you could find yourself unable to even run on the A side.

This

was a bigger problem previous to the TR because the TD at least

forces

them equal a couple times a year.

Now if you want to do your PTFs smoothly and just stay out of trouble

you

WILL Perm apply. This sort of sequence:

DoUntil Upgrade *eq *YES

FULL SAVE
Load/apply PTFs
SAVE IBM

Run for a while (Your call, month or two perhaps)

APYPTF *ALL *PERM
IPL
SAVE IBM

Run for a while (your call, month or two perhaps)

Enddo

Follow this pattern and you and your system will be happy and

applying

PTFs will run smoothly with near zero issues.

- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 3/2/2018 8:27 PM, Robert Hooper wrote:

So I've run across something interesting. I was talking with

someone

about applying the latest cume / group PTF on a V7R1 server that has

not

had PTF's applied in over 3 years. When I asked if the existing PTF's

had

been perm applied, the response I got was that they never apply the

PTF's

perm but keep applying temp.

Does anyone else do this? I've always done the apply cume temp,

let it

bake until the next pack comes out, apply perm before SAVSYS (at

least),

then apply next cume pack.

Is this not the way of PTF care and feeding?

Thanks

Robert

Sent from my iPhone

--
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/m

idrange-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
--
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

--
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021

NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you

received

this communication in error, please contact the sender and

delete/destroy

all copies of this communication immediately.
--
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

--
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021

NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.
--
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

--
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021

NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.

--
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021

NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.