Re: V7R1 to V7R3 upgrade prep - perm apply PTFs

After perm apply of the PTFs.

DLTPTF PTF(*PRMAPY) LICPGM(*ALL)

3591 PTFs deleted.

3,591 cover letters removed from QGPL/QAPZCOVER
3,964 savf deleted from QGPL.

Paul




-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Jim Oberholtzer
Sent: Wednesday, February 21, 2018 5:07 PM
To: Midrange Systems Technical Discussion
Subject: Re: V7R1 to V7R3 upgrade prep - perm apply PTFs

Paul:

You need to think about where the PTF is. The Permanent area is different
from the temp area, we all know that. Applying the PTF permanently
requires the system to copy that code into the perm area. If the object is
active it can't do that. As you discovered most PTFs will it copy, there
are those in the LIC and in OS that are always active and can't be copied.

Jim Oberholtzer
CEO/Chief Technical Architect
Agile Technology Architects

On Wed, Feb 21, 2018 at 2:58 PM, Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
wrote:

I'm preparing for this weekend's final V7R1 to V7R3 upgrade,
production LPAR I was permanently apply all PTFs.

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

There are about 20 SI PTFS, that remained temporarily applied,
requiring an IPL to perm apply.
I thought once a PTF was applied, an IPL was no longer needed.

Any thoughts from the group?

Message ID . . . . . . : CPF3994
Date sent . . . . . . : 02/21/18 Time sent . . . . . . :
16:44:54

Message . . . . : Delayed PTF 5770SS1-SI51332 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).

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