HMC/FSP upgrade questions....

All,

We are planning an upgrade to our HMC code & FSP firmware. Since this is something that's done once in a blue moon, need some advice relative to the "disruptiveness" or lack thereof relative to this procedure. I have read much of the available documentation IBM released, and find it confusing, so please no references that aren't explicit. (I say confusing because some IBM'ers I have spoken to say disruptive, but the information from fix central copied below, says otherwise. Notice how it directly references p5 but not i5. This bothered me as well.)

Environment:
9406-570 (dual service processors)
HMC - 6.1.3
FSP level - SF240-320-201
 
Targeted upgrade:
HMC - 7.3.4 with latest service packs
FSP - SF240-358-201

Obviously I know there are some HMC recycles involved, but I am only concerned with managed system disruptions. Those that have done upgrades of this nature please chime in. Thanks 

3.0 Firmware Information and DescriptionIBM introduced the Concurrent Firmware Maintenance (CFM) function on p5 systems in system firmware level SF230_126_120, which was released on June 16, 2005.  This function supports nondisruptive system firmware service packs to be applied to the system concurrently (without requiring an IPL to activate changes).
For systems that are not managed by an HMC, the installation of system firmware is always disruptive.
Note:  The concurrent levels of system firmware may, on occasion, contain fixes that are known as deferred. These deferred fixes can be installed concurrently, but will not be activated until the next IPL.  Deferred fixes, if any, will be identified in the "Firmware Update Descriptions" table of this document.  For deferred fixes within a service pack, only the fixes in the service pack which cannot be concurrently activated are deferred.
Use the following example as a reference to determine whether your installation will be concurrent or disruptive.
Note:  The file names and service pack levels used in the following examples are for clarification only, and are not
             necessarily levels that have been, or will be released.
System firmware file naming convention:
     01SFXXX_YYY_ZZZ
* XXX is the release level
* YYY is the service pack level
* ZZZ is the last disruptive service pack level NOTE:  Values of service pack and last disruptive service pack  level (YYY and ZZZ) are only unique within
a release level (XXX).  For example, 01SF235_250_120 and 01SF240_250_200 are different service packs.
An installation is disruptive if:
* The release levels (XXX) are different.               Example:  Currently installed release is SF225, new release is SF230
* The service pack level (YYY) and the  last disruptive service pack level (ZZZ) are equal.                Example:  SF230_120_120 is disruptive, no matter what level of SF230 is currently
                                   installed on the system
* The service pack level (YYY) currently installed on the system is lower than the last disruptive service pack level (ZZZ) of the service pack to be installed.                  Example:  Currently installed service pack is SF230_120_120 and
                                     new service pack is SF230_152_130
An installation is concurrent if:
* The release level (XXX) is the same.
* The service pack level (YYY) is the same or higher than the service pack level currently installed on your system.               Example: Currently installed service pack  is SF230_126_120,
                                 new service pack is SF230_143_120.