There appears to be a misunderstanding here of what constitutes a
disruptive firmware update.
In the case being quoted the user was going from
FW910.11 VL910_122_089
to
FW910.10 VL910_115_089 /
from the readmes; 01VLxxx_yyy_zzz
The release level is the same - VL910 (xxx)
The service pack level (yyy) on the old code is greater than the
disruptive service pack level (zzz) on the new code.
The code is (or should be) being applied by an HMC 7063-CR1
So the code itself is NOT disruptive in this case.
That being said .... there are deferred fixes on the new VL910_122_089 /
FW910.20 code level and also on the intermediate VL910_115_089 / FW910.11
version.
This means that the code can be applied concurrently with system
operations and at the point in time that you choose - the deferred fixes
are picked by by either a platform power cycle or if stated a partition
IPL.
It may well be that the Deferred fixes are for features or function that
do not apply to your operations - in that case you would never need to
schedule an outage to pick them up. (in this case though I would be
scheduling an outage to pick them up)
Deferred fix
The installation of a deferred fix is concurrent (nondisruptive) to
customer operations. However, the fix will not become active until an IPL
(system level) is performed.
As to Permanently Applying the Firmware - I never bother. It will be
permanently applied the next time a disruptive code upgrade is applied on
the system.
I release the above may be construed to be splitting hairs - but it is
important to get the terminology correct.
Regards
Shaun
  Â
[1]167 Main North Road
Private Bag 4705
Shaun Ryan Christchurch 8140Â
Systems Administrator SAP Basis   [2]P: +64 3 363 6939
 [3]M: +64 21 974 587
[4]E: Shaun.Ryan@xxxxxxxxxxxxxxxxxxx
[5]www.foodstuffs-si.co.nz
-----Original Message-----
From: Steinmetz, Paul via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>
Sent: Tuesday, 26 February 2019 5:58 a.m.
To: 'midrange-l@xxxxxxxxxxxxxxxxxx' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Subject: RE: Perm Apply of Firmware....
Andrew,
I just applied VL910_122 FW910.20 MH01799 firware.
I did a power down of the server to apply the "disruptive" firmware.
However, I'm not sure if they applied.
This is my first firmware apply on P9 and 7063-CR1.
Did the process change for applying "disruptive" firmware?
Service partition . . . . . . . . . . . . . . . . : No
Firmware update policy . . . . . . . . . . . . . . : *HMC
Server IPL source . . . . . . . . . . . . . . . . : Temporary
Firmware product ID/release . . . . . . . . . . . : 5733909 V1R1M0
Update access key expiration date . . . . . . . . : 01/16/22
---Server firmware----
Fix PTF
Copy pack ID
*ACTIVE VL910_122 MH01799 FW910.20
*TEMP VL910_122 MH01799 FW910.20
*PERM VL910_115 MH01798 FW910.11
Paul
-----Original Message-----
From: MIDRANGE-L [[6]mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On
Behalf Of Andrew Lopez (SXS US)
Sent: Monday, February 25, 2019 11:44 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Perm Apply of Firmware....
There's plenty of comments in the archives (and on-line) about the need
for a power down being needed when applying disruptive firmware upgrades
from an HMC. I may be missing it, but now that I have done that, and I
have the new firmware on both the *ACTIVE and *TEMP copies, will I need
that deep reboot for the *PERM apply?
For the record, our DSPFMWSTS on the sole partition shows:
Service Partition Yes
Firmware update policy *HMC
Server IPL source *Temporary
Firmware product ID/Release 5733909 V1R1M0
Update access key expiration date 07/21/21
*ACTIVE VL910_122 FW910.20 MH01799
*TEMP VL910_122 FW910.20 MH01799
*PERM VL910_073 FW910.00 MH01712
Fix pack, PTF ID and Update Status all show as *NONE/None.
I assume that using the green screen to *PERM apply all PTFs won't be
enough to get the firmware copied to *PERM at the next IPL. What I can't
tell is if the *PERM apply is as disruptive as the *TEMP apply.
_____________________________________________________________________
Spirax-Sarco Engineering Plc. This e-mail has been scanned for viruses by
Cisco Cloud Email Security.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [7]
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [8]
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: [9]
https://amazon.midrange.com
------------------------------------------------------------------------------------------------------------------------
Note:
This e-mail message has been inspected for malicious content.
Attention:
The information contained in this message and or attachments is intended
only for the person
or entity to which it is addressed and may contain confidential and/or
privileged material. Any
review, retransmission, dissemination or other use of, or taking of any
action in reliance upon,
this information by persons or entities other than the intended recipient
is prohibited. If you
received this in error, please contact the sender and delete the material
from any system and
destroy any copies.
Please note that the views and opinions expressed in this message may be
those of the
individual and not necessarily those of Foodstuffs South Island Ltd.
Thank you.
------------------------------------------------------------------------------------------------------------------------
References
Visible links
1.
https://www.google.co.nz/maps/place/Foodstuffs+South+Island+Limited/@-43.4860111,172.6155373,15.45z/data=!4m5!3m4!1s0x0:0x83f21f1bdb963e47!8m2!3d-43.4863573!4d172.6152563
2. file:///tmp/tel:+64 3 363 6939
3. file:///tmp/tel:+64 21 974 587
4. mailto:Shaun.Ryan@xxxxxxxxxxxxxxxxxxx
5.
http://www.foodstuffs-si.co.nz/
6. mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx]
7.
https://lists.midrange.com/mailman/listinfo/midrange-l
8.
https://archive.midrange.com/midrange-l.
9.
https://amazon.midrange.com/
midrange.com
