IBM Power 770, Technical Overview And Introduction

Page: 73 / 220

Chapter 2. Architecture and technical overview
59
The On/Off CoD process consists of three steps: enablement, activation, and billing.
򐂰 Enablement
Before requesting temporary capacity on a server, you must enable it for On/Off CoD. To
do this, order an enablement feature and sign the required contracts. IBM will generate an
enablement code, mail it to you, and post it on the web for you to retrieve and enter on the
target server.
A
processor enablement
code allows you to request up to 360 processor days of
temporary capacity. If the 360 processor-day limit is reached, place an order for another
processor enablement code to reset the number of days that you can request back to 360.
A
memory enablement
code lets you request up to 999 memory days of temporary
capacity. If you reach the limit of 999 memory days, place an order for another memory
enablement code to reset the number of allowable days you can request back to 999.
򐂰 Activation requests
When On/Off CoD temporary capacity is needed, use the HMC menu for On/Off CoD.
Specify how many inactive processors or gigabytes of memory are required to be
temporarily activated for some number of days. You are billed for the days requested,
whether the capacity is assigned to partitions or remain in the shared processor pool.
At the end of the temporary period (days that were requested), you must ensure that the
temporarily activated capacity is available to be reclaimed by the server (not assigned to
partitions), or you are billed for any unreturned processor days.
򐂰
Billing
The contract, signed by the client before receiving the enablement code, requires the
On/Off CoD user to report billing data at least once a month (whether or not activity
occurs). This data is used to determine the proper amount to bill at the end of each billing
period (calendar quarter). Failure to report billing data for use of temporary processor or
memory capacity during a billing quarter can result in default billing equivalent to 90
processor days of temporary capacity.
For more information about registration, enablement, and usage of On/Off CoD, visit the
following location:
http://www.ibm.com/systems/power/hardware/cod
2.4.3 Utility Capacity on Demand (Utility CoD)
Utility CoD automatically provides additional processor performance on a temporary basis
within the shared processor pool.
With Utility CoD, you can place a quantity of inactive processors into the server’s shared
processor pool, which then becomes available to the pool's resource manager. When the
server recognizes that the combined processor utilization within the shared processor pool
exceeds 100% of the level of base (purchased and active) processors that are assigned
across uncapped partitions, then a Utility CoD processor minute is charged and this level of
performance is available for the next minute of use.
If additional workload requires a higher level of performance, the system automatically allows
the additional Utility CoD processors to be used, and the system automatically and
continuously monitors and charges for the performance needed above the base (permanent)
level.