HP-UX Workload Manager A.03.02.xx Release Notes for HP-UX 11i v1, HP-UX 11i v2, and HP-UX 11i v3

HP-UX Workload Manager Release Notes
Patches and fixes in this version
45
Beginning with this release of WLM, a new global arbiter configuration keyword
(utility_reserve_threshold) enables you to increase or decrease this threshold. The
default is 15 days. The following example shows the threshold set to 5 days, causing WLM to
continue allocating temporary capacity until 5 or fewer days of temporary capacity resources
are available:
par {
utility_reserve_threshold = 5;
}
You can set the keyword to 0 to cause WLM to always activate temporary capacity resources
as long as any number of temporary capacity resources are available. Note that it is
recommended that some quantity of temporary capacity always be kept in reserve. Having a
buffer of temporary capacity allows you to avoid delays activating additional cores when a
purchase of additional capacity is necessary. For more information, see the HP-UX Workload
Manager User’s Guide or wlmparconf(4). For information on additional restrictions involving
activation of temporary capacity resources, see the Instant Capacity (iCAP) documentation.
This fix addresses CR# JAGaf97368.
prmmonitor does not display memory “Upper Bound” for WLM
groups
In a WLM configuration that includes workload groups for which gminmem, gmaxmem, and
memweight are specified, the prmmonitor MEM command fails to display the current PRM
memory cap in the “Upper Bound” column. This problem occurs when using prmmonitor to
check the memory entitlement and usage for each group.
A new “MB Max” column has been added to the prmmonitor MRG command display, showing
the maximum amount of memory available to the group. Because this enhancement is
introduced in PRM C.03.02, that version of PRM (or later) must be installed on your system in
order to get the new prmmonitor MRG display.
Note that starting with WLM A.03.02, the wlminfo group command has been enhanced to
display memory utilization of all groups in the current deployed configuration, and used with
the -v option, displays each group’s gmincpu, gmaxcpu, gminmem, and gmaxmem values, if they
are available. The new -v option is ignored if live data is not being displayed (for example,
when the -o option is being used). If memory management is not being used, a dash (-)
instead of a zero is displayed in the ‘Mem Shares’ column. If a group’s gmincpu, gmaxcpu,
gminmem, or gmaxmem value is not assigned in the current configuration, a dash (-) is displayed
in the corresponding column.
This enhancement addresses CR# JAGaf86413.