HP-UX Workload Manager User's Guide

Managing SLOs across partitions
Setting up your WLM global arbiter configuration file
Chapter 7 275
(or less than) integer, you must purchase additional
resources. Before adding capacity, be sure to stop
wlmpard (using the -k option) and all wlmd clients on
the complex. You can set the keyword to 0 to cause the
global arbiter to always activate temporary capacity
resources as long as any number of temporary capacity
resources are available.
If you assign a value that is too high, the amount of
temporary capacity can reach the threshold too quickly,
causing WLM to stop using temporary capacity sooner
than preferred. Although you can set the value to 0
(enabling WLM to activate temporary capacity as long
as any amount is available), you could set the value too
low in certain circumstances, such as on systems with
large workloads. When the value is too low, temporary
capacity could be consumed so quickly that WLM might
not detect the threshold breach in time and would
continue allocating reserves that no longer exist. This
would result in errors when WLM attempts to move
these temporary capacity cores across partitions. For
information on additional restrictions involving
activation of temporary capacity resources, see the
Instant Capacity (iCAP) documentation.
NOTE HP recommends keeping some quantity of temporary capacity in reserve.
Purchase of TiCAP codewords (required to activate additional temporary
capacity cores) may take one or more days, so having a buffer of
temporary capacity allows you to avoid delays in activation of additional
cores. Instant Access Capacity (IAC) is provided with the initial purchase
of a temporary capacity component to give you an immediate buffer of
temporary capacity in case extra capacity is needed before you can
purchase a TiCAP codeword. However, IAC only provides an initial
buffer; ongoing purchases of additional temporary capacity are
recommended to replenish this capacity.