I had similar behavior with V7R1 TR9 and latest CUM on one LPAR when TR9 was not yet applied.
On the other LPAR, where TR9 was already applied, this behavior did not occur.

The 2nd LPAR, MF99009 was included to be applied with the other PTFs The below messages occurred, several of the CPF36BD, during option 8, load from service.
Before I did my PWRDWNSYS, I had many PTFs that were still in *SAVF status, not loaded, nor set to be applied.
During the PWRDWNSYS, watching the IPL process, these PTFs that were not loaded did get loaded and applied.
I expected another PWRDWNSYS would be need to load and apply these missed PTFs, but that was not the case.

CPF3611 Diagnostic 40 11/19/14 22:04:53.966714 QPZINSFX QSYS 16AE QPZPTFIN QSYS 0602
Message . . . . : PTF 5770999-MF99009 V7R1M0 requires IPL.
Cause . . . . . : PTF 5770999-MF99009 V7R1M0 must be permanently applied
before the remaining PTFs can be loaded and applied. PTF 5770999-MF99009
V7R1M0 is a technology refresh requisite PTF required by one or more of the
PTFs being loaded. Recovery . . . : Perform a normal mode IPL to the B
IPL source and then try the request again.

CPF362E Diagnostic 40 11/19/14 22:04:53.969464 QPZINSFX QSYS 1729 QUICMENU QSYS 00C1
Message . . . . : IPL required to complete PTF install processing.
Cause . . . . . : At least one PTF requires an initial program load (IPL) to
complete the PTF install processing. This includes one or both of the
following: -- A technology refresh PTF or its requisite PTFs requires an
IPL. A technology refresh PTF must be permanently applied before the
remaining PTFs can be loaded and applied. -- One or more special handling
PTFs or its requisite PTF requires an IPL. There are special handling PTFs
defined in a PTF group being installed that must be applied before the
remaining PTFs in the PTF group can be applied. Recovery . . . : Perform
a normal mode IPL from the B IPL source to complete the PTF install. During
the next unattended IPL, the remaining PTFs will be installed. If an IPL is
required for a technology refresh PTF, device *SERVICE and image catalog
*NONE will be used to load the additional PTFs during the next IPL. See the
previously listed messages for PTFs that require an IPL.

CPF36BD Diagnostic 30 11/19/14 22:48:03.295954 QPZLPC QSYS 110F QPZINSFX QSYS 0845
Message . . . . : PTF MF99009 prevented load of PTF MF58863.
Cause . . . . . : The program temporary fix (PTF) 5770999-MF58863 being
loaded has a technology refresh requisite PTF 5770999-MF99009. The
technology refresh PTF 5770999-MF99009 or its superseding PTF is not
permanently applied. Recovery . . . : Do one of the following, and then
try the Load PTF (LODPTF) command again: -- Specify *APYPERM for the
superseded PTFs (SPRPTF) parameter. For Licensed Internal Code PTFs, the
system must be operating on the B IPL source. -- Permanently apply (APYPTF
command) PTF 5770999-MF99009 or its superseding PTF.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Massiello - ML
Sent: Monday, December 08, 2014 12:46 PM
To: Midrange Systems Technical Discussion
Subject: RE: V7R2M0 TR ptf requires second IPL

Rob,

When you go to IPL the machine, you should have the Image Catalog loaded and ready with the virtual optical. I have applied about 12 or more TR1s on 7.2 and never ever had to manually do a 2nd IPL. The machine under the covers does the IPL for you, and you can actually see it do this if you watch the SRCs and the console. You will note that not all the PTFs are even set to apply, but when you are done the entire TR, Cume, and Groups have been applied.

Pete

--
Pete Massiello
iTech Solutions
http://www.itechsol.com
http://www.iInTheCloud.com




-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, December 08, 2014 12:08 PM
To: midrange-l@xxxxxxxxxxxx
Subject: V7R2M0 TR ptf requires second IPL

V7R2M0 TR ptf requires second IPL
and apparently that second IPL is not just something that is automatically done.

call qvoifimg PARM('CUME ' '*ALL ' 0)
LODIMGCLG IMGCLG(CUME) DEV(OPTVRT01)
VFYIMGCLG IMGCLG(CUME) TYPE(*PTF) SORT(*YES) Image catalog CUME, type *PTF verified.
INSPTF LICPGM((*ALL)) DEV(OPTVRT01) INSTYP(*DLYALL)
CPF3611
Message . . . . : PTF 5770999-MF99101 V7R2M0 requires IPL.
Cause . . . . . : PTF 5770999-MF99101 V7R2M0 must be permanently applied

before the remaining PTFs can be loaded and applied. PTF
5770999-MF99101
V7R2M0 is a technology refresh requisite PTF required by one or more of the
PTFs being loaded.

So, I have to IPL,
rerun the INSPTF
IPL again,
right?

I'll probably run the
CHGIPLA STRPRTWTR(*NO) STRRSTD(*YES)
before the first IPL to make the system come up in restricted state to ease starting the second IPL.



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

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


This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].