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

Known problems and workarounds

Temporary Instant Capacity (TiCAP) expires while WLM is managing

nPartitions

Issue WLM manages nPartitions using its wlmpard daemon. Assume wlmpard is

started on a system that has Temporary Instant Capacity in use. If that

temporary capacity expires, wlmpard will still be able to deactivate cores

without any problems. However, wlmpard may attempt to activate cores

based on the expired capacity. These attempts will fail because the

temporary capacity no longer exists. wlmpard will not abort, but it may

continue to attempt to activate unavailable cores, generating a message of

the following form in /var/opt/wlm/msglog:

Error increasing core count on partition par_name (has x needs

y).

You will also see the message:

Unable to set the local partition to z cores. Check the

partition status.

where x, y, and z represent integer values.

Workaround Add a utilitypri statement to your wlmpard configuration, say

configuration_file, and then load the new file:

# /opt/wlm/bin/wlmpard -a configuration_file

The utilitypri keyword allows WLM—when Temporary Instant Capacity

is available—to adjust the total cores to meet demand.

Specifying this priority ensures WLM maintains compliance with your

Temporary Instant Capacity usage rights. When your prepaid amount of

temporary capacity expires, WLM no longer attempts to use the temporary

resources.

NOTE Beginning with WLM A.03.02, you can set a threshold that

determines when WLM will stop allocating temporary

capacity resources. Prior to WLM A.03.02, the threshold was

fixed at 15 processing days (where WLM stops allocating

temporary capacity if 15 or fewer processing days of

temporary capacity remain available). For more information,

see “WLM Temporary Instant Capacity 15-day threshold too

limiting” on page 42 and wlmparconf(4).