An LPAR can be added, removed, activated, or deactivated at any time. Changing the number  of LPARs is not disruptive and does not require a POR. Certain facilities might not be  available to all operating systems because the facilities might include software corequisites. Known as  l ogical processors , they can be defined as CPs, IFLs, ICFs, or zIIPs. They can  be dedicated to an LPAR or shared among LPARs. When shared, a processor weight can  be defined to provide the required level of processor resources to an LPAR. Also, the  capping option can be turned on, which prevents an LPAR from acquiring more than its  defined weight and limits its processor consumption. LPARs for z/OS can have CP and zIIP logical processors. The two logical processor types  can be defined as all dedicated or all shared. The zIIP support is available in z/OS. The weight and number of online logical processors of an LPAR can be dynamically  managed by the LPAR CPU Management function of the Intelligent Resource Director  (IRD). These functions can be used to achieve the defined goals of this specific partition  and of the overall system. The provisioning architecture of z14 ZR1 servers (as described  in Chapter 8, “System upgrades” on page 281) adds another dimension to the dynamic  management of LPARs. PR/SM is enhanced to support an option to limit the amount of physical processor  capacity that is used by an individual LPAR when a PU is defined as a general-purpose  processor (CP) or an IFL that is shared across a set of LPARs. This enhancement is designed to provide a physical capacity limit that is enforced as an  absolute (versus relative) limit. It is not affected by changes to the logical or physical  configuration of the system. This physical capacity limit can be specified in units of CPs or  IFLs. The Change LPAR Controls and Customize Activation Profiles tasks on the HMC  were enhanced to support this new function. For the z/OS Workload License Charges (WLC) pricing metric and metrics that are based  on it, such as Advanced Workload License Charges (AWLC), an LPAR  defined capacity can be set. This defined capacity enables the soft capping function.  Workload charging introduces the capability to pay software license fees that are based on  the processor use of the LPAR on which the product is running, rather than on the total  capacity of the system. Consider the following points: The defined capacity value is specified on the Options tab in the Customize Image  Profiles window. Each LPAR has the following resources that are the same as a real CPC: GLYPH<SM590000> Processors – In support of WLC, the user can specify a de fined capacity in millions of service units  (MSUs) per hour. The defined capacity sets the capacity of an individual LPAR when  soft capping is selected. – WLM keeps a four -hour rolling average of the processor usage of the LPAR. When the  four-hour average processor consumption exceeds the defined capacity limit, WLM  dynamically activates LPAR capping (soft capping). When the rolling four-hour average  returns below the defined capacity, the soft cap is removed. For more information about WLM, see  System Programmer's Guide to: Workload  Manager , SG24-6472.  For more information about software licensing, see 7.8, “Software licensing” on page 277. 98  IBM 14 Model ZR1 Technical Guide