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

How the peak four-hour rolling average MSU value is determined

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

Table 1 shows an example of how the peak four-hour rolling average MSU value is calculated for the combination of products and LPARs shown in Figure 1.

Table 1. Example of calculating the peak utilization based on the peak four-hour rolling average MSU value
Utilization

Hour
1

Hour
2

Hour
3

...

Hour
719

Hour
720

LPAR1: Four-hour rolling average utilization 60 55 50 ... 50 45
LPAR2: Four-hour rolling average utilization 70 80 75 ... 75 70
z/OS® utilization (LPAR1 + LPAR2) 130 135 125 ... 125 115
MQSeries® and IMS™ utilization (in LPAR1 only) 60 55 50 ... 50 45
CICS® and DB2® utilization (in LPAR2 only) 70 80 75 ... 75 70

The peak interval is the highest utilization determined from the sum of the utilization for all LPARs in which a particular product ran in a given hour. It is not the sum of highest utilization for individual LPARs in which a particular product ran during different hours.

In this example, the peak interval for z/OS is in hour 2. The z/OS utilization value for the month is the sum of the z/OS utilizations in both LPARs during hour 2, or 135.

The peak interval for MQ Series and IMS is in hour 1. Since those products only run in LPAR 1, their utilization value for the month is the value for LPAR 1 in hour 1, or 60.

The peak interval for CICS and DB2 is in hour 2. Since those products only run in LPAR 2, their utilization value for the month is the value for LPAR 2 in hour 2, or 80.

 Notices | Terms of use | Support | Contact z/OS | zFavorites Copyright IBM Corporation 1990, 2014