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

If WLM cannot increase a partition’s CPU resources, the wlminfo par

command displays the wrong CPU (core) count

If WLM is not able to increase a partition’s CPU resources (number of cores), the wlminfo par

command erroneously displays the same value for both the intended and actual core count.

For example, if WLM fails to raise the count on a partition from 2 to 3, wlminfo par should

display the intended core count as 3 and the actual core count as 2; however, the command

displays both the intended and actual count as 3.

The wlminfo par command has been fixed to display the intended and actual core counts

correctly.

This fix addresses CR# JAGaf88801.

WLM issues vparstatus failure warnings that can be ignored

If the vparstatus command is used immediately after you use the vparmodify command, the

vparstatus command might fail. The failure occurs because the virtual partition database is

still locked by the virtual partition monitor. As a result, WLM issues the following warning:

vPar command failures seen while gathering partition status information.

This message can be ignored unless any of the following conditions occur:

• WLM issues error messages indicating that modifications of cores are failing

• System users notice that expected migrations of cores fail to happen

Beginning with WLM A.03.02, WLM is less likely to issue the command failure warning, as it

now ignores vparstatus failures up until the last vparstatus call during modification of a

virtual partition.

This fix addresses CR# JAGaf86468.

wlmpard ignores Temporary Instant Capacity (TiCAP) capacity

changes

Starting with WLM A.03.00, when utilitypri is enabled (in the global arbiter configuration

file), wlmpard fails to notice temporary capacity changes once all hosts have connected. It only

detects changes when a new host connects. As a result, when the amount of reserve capacity

falls below the threshold (15 processing days by default, or the number of days specified with

the utility_reserve_threshold keyword), wlmpard might continue to activate temporary

capacity.

Beginning with WLM A.03.02, wlmpard will detect such changes and stop allocating reserve

capacity after the threshold is reached.