HP-UX Workload Manager A.03.05.xx Release Notes for HP-UX 11i v3

“Shutdown initiated” message. This most likely means that the partition
modifications have not yet completed. They can take longer than 120 seconds.
When the modifications have been made, WLM will honor the shutdown request.
You can verify the shutdown has succeeded by using the ps command (if
necessary, issue your shutdown command again). In addition, check the messages
in /var/opt/wlm/msglog.
Unable to get CPU allocation due to number of processes
Issue WLM provides a workload group its allocation on a system by granting the group
its allocation on each core. If the group does not have at least one process for
each core, WLM increases the allocations for the processes to compensate. For
example, for a workload group with a single-threaded process, 10% of four cores
is allocated as 40% of one core.
Assume this same group were allocated 50% of the four cores. WLM would
allocate 100% of two cores to the workload group. However, because the group
has only the one thread, it can use only one core, resulting in an allocation of
25%.
Workaround There is no workaround. However, be aware of how your applications run so
that you do not give them resource allocations they cannot use.
Collectors abort when updated while running
Issue If you update (overwrite) a data collector executable (be it a binary or a script)
while it is providing data to WLM, the collector may abort.
Workaround There are two workarounds to this issue:
• Update the data collector in place
Stop WLM (wlmd -k)1.
2. Update the data collector
3. Re-start WLM (wlmd -a configuration_file)
• Replace the data collector
1. Move the current data collector aside
2. Install the new data collector in place of the collector you just moved
aside
3. Re-start WLM (wlmd -a configuration_file)
GlancePlus/OpenView Performance Agent and processor sets
Issue On systems with multiple processor sets configured, GlancePlus may have incorrect
data for the PRM_SYS group (ID 0). On these systems, GlancePlus will incorrectly
include processes that are outside of the default processor set as belonging to
the PRM_SYS group (ID 0).
As a result, the WLM glance_prm data collection script cannot be used to track
application (APP or APP_PRM) metrics for the PRM_SYS group or any PRM group
defined based on a PSET.
Only GlancePlus is affected by this issue—WLM properly identifies workload
groups (PRM groups and their PRM IDs).
Workaround For HP-UX 11i v1 (B.11.11), using GlancePlus C.03.55 or later and installing
patch PHKL_28052 addresses this issue.
For HP-UX 11i v2 (B.11.23), this issue is fixed in GlancePlus C.03.58.05.
10 Known problems and workarounds