z/OS Planning for Sub-Capacity Pricing
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Implications of a defined capacity

z/OS Planning for Sub-Capacity Pricing
SA23-2301-00

Defined capacity is an LPAR setting available to LPARs that:
  • Are in a zEnterprise® System, System z10®, or System z9® environment or on zSeries® hardware
  • Are running native z/OS® systems in 64-bit mode (Defined capacity is not supported for z/OS systems that are z/VM® guests.)
  • Use shared general purpose CPs
  • Have relative weight not enforced (no PR/SM™ hard cap set)

Defined capacity is an optional setting that can be changed dynamically. Use the Hardware Management Console (HMC) to establish or change a defined capacity. You can also establish a defined capacity in the LPAR Image Profile, which ensures that the desired defined capacity is used if the system is re-IPLed. The defined capacity setting is in terms of MSUs. In cases where there are different values for hardware MSUs and software pricing MSUs for a given CPC, the defined capacity should be established in terms of software pricing MSUs. If you establish a defined capacity for an LPAR that has a PR/SM hard cap (enforced relative weight) or dedicated CPs, the defined capacity is ignored.

If you establish a defined capacity in an LPAR, z/OS workload management (WLM) monitors the four-hour rolling average utilization of that LPAR. If the four-hour rolling average utilization of the LPAR exceeds the defined capacity, the LPAR is temporarily capped (this is called soft capping) until the four-hour rolling average drops back below the defined capacity. The LPAR four-hour rolling average utilization can exceed the defined capacity. However, if the four-hour rolling average does exceed the defined capacity and soft capping is applied, it is possible (while being soft-capped) for the four-hour rolling average to continue to rise and to exceed the defined capacity. In these cases, SCRT reports the defined capacity value and IBM® charges customers at the defined capacity level rather than based upon the higher four-hour rolling average utilization.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014