Although a prior message by PaulMmn showed APYPTF LICPGM(*ALL), there
was an implication specific only to LIC PTFs; i.e. mention of running on
the B-side, and reference to A-side. The rules are different for LIC
than for OS and LPPs. Anyhow, the docs for non-IPL permanent
application of PTFs:
IBM i 7.1 Information Center -> IBM i and related software ->
Maintaining and managing IBM i and related software -> Using software
fixes -> Installing fixes -> Advanced procedures for fix installation ->
Applying fixes
_i Advanced fix installation: Applying fixes without an IPL i_
http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/topic/rzam8/rzam8fixinstallapplynoipl.htm
"To temporarily or permanently install immediate IBM® i fixes without
doing an IPL, follow these steps.
...
7. Specify *NO for the Delayed PTFs (DELAYED) parameter.
Note: To apply all immediate fixes right now and all delayed fixes on
the next IPL, specify *ALL for the Product (LICPGM) parameter, *ALL for
the Select (SELECT) parameter, and *IMMDLY for the Apply Type (APPLY)
parameter.
...
"
Note: I have sent feedback about the incorrect reference to a
non-existent parameter "Apply Type (APPLY)" [above; step 7 "Note:"],
suggesting that the text should refer to the parameter "Delayed PTFs
(DELAYED)".
_Advanced fix installation: Applying Licensed Internal Code fixes_
_without an IPL_
http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/topic/rzam8/rzam8fixinstallapplylicnoipl.htm
"To determine how to apply Licensed Internal Code fixes without an IPL,
follow these procedures.
You may be operating from either storage area to temporarily install an
immediate Licensed Internal Code fix without doing an IPL. You must be
operating from the B storage area to permanently install a temporarily
installed Licensed Internal Code fix without doing an IPL.
..."
FWiW: I can not recall why a non-LIC PTF [with neither activation
instructions nor exit program(s)] that was created as limited to only
delayed application would not be eligible to be permanently applied
without an IPL. With only a cursory review in my mind, of the process
of applying PTFs, I can think of almost nothing that should prevent the
typical permanent apply being done immediate vs delayed; at least
ignoring an attempt to maintain consistency with the parameter naming
"DELAYED", for both *TEMP and *PERM apply. Perhaps some cases whereby
the old code [renamed, in product library] is still running or could
still run on the current IPL [such that a perm apply moving the
activated object into QRPLOBJ would be undesirable].? And if so, I
wonder if those would be rare enough, that those specific affected PTFs
could be specially tagged as such, while allowing most "delayed" PTFs to
permanently apply without an IPL? Maybe someone else who knows will
comment.? As if anyone will read this ;-)
Regards, Chuck
On 01 Jun 2012 12:35, rob@xxxxxxxxx wrote:
Hey, I tried an
APYPTF LICPGM(5770SS1) APY(*PERM)
Got message CPF3994
Message: Delayed PTF 5770SS1-SI41322 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).
So, apparently even if a PTF is already temporarily applied and you
just want to move it to permanently applied it's best to do that at
IPL time (at least for delayed PTFs). Earlier we discussed maybe we
just had to do that when temp applying them.
midrange.com
