HP-UX Workload Manager A.03.04.xx Release Notes

# icapstatus -M
global:n:64:0:29:0:0:0.000:0.000:0:0:0:
npar:Partition 0:0:n:32:3:8:3:29:29:8:8:0:90.000:90.000:0.000:
npar:Partition 1:1:n:32:32:8:32:0::8:8:0:78.000:78.000:0.000:
vpar:okra04:0:y:1::1:1:0:29:::::::
vpar:virt10:0:n:1::1::::::::::
vpar:virt14:0:n:1::1::::::::::
In the output, if the 'global' line includes an 'n' and partitions are listed, WLM
is affected.
Workaround
Run icapstatus with no options. If the output shows that the number of
inactive cores is:
• 0
Run icapmodify -a 0.
• > 0
Run icapmodify -a n, where n is the number of inactive cores.
Application hangs in FSS group
Issue On HP-UX 11i v2 (B.11.23), an application inside a workload group based on
an FSS group may hang when running in a single-processor virtual partition,
nPartition, or system.
Workaround Install patch PHKL_33052.
Shutdown slow; “Waiting for shutdown confirmation” and “Shutdown
initiated; however, ... unable to acquire confirmation” messages displayed
Issue In some situations, WLM might take longer than expected to shut down,
especially when WLM is in the process of modifying the distribution of CPU
resources among partitions. In such cases, the shutdown request will not be
honored until the modifications are completed. Beginning with WLM A.03.02,
you might see the following message after 30 seconds:
Waiting for shutdown confirmation...
Then, if no shutdown confirmation is received within the next 90 seconds, WLM
will display the following message:
Shutdown initiated; however, we were unable to acquire
confirmation. Check the messages in /var/opt/wlm/msglog
for more details.
In versions of WLM prior to A.03.02, under similar circumstances you would
get one of the following messages after 30 seconds:
wlmd -k failed: Resource temporarily unavailable
wlmpard -k failed: Resource temporarily unavailable
wlmcomd -k failed: Resource temporarily unavailable
These messages are misleading in that they imply that the shutdown request
had failed when it might not have. These messages have been replaced by the
more accurate messages reported above.
Workaround If a shutdown request has been delayed for 30 seconds, WLM issues the
“Waiting for shutdown confirmation” message. WLM is likely delaying
the shutdown request while waiting for partition modifications to complete. If
after a total of 120 seconds the shutdown has still not completed, WLM issues
the “Shutdown initiated” message. This most likely means that the partition
Application hangs in FSS group 15