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

GlancePlus may not correctly identify processes’ PRM groups
Issue On some systems, GlancePlus would not correctly identify processes’ PRM groups.
WLM uses these PRM groups as its workload groups. On these systems,
GlancePlus would report all processes as belonging to the PRM_SYS group (ID
0). As a result, the WLM glance_prm data collection script could not be used
to track application (APP) metrics for a PRM group of processes.
Workaround This issue is fixed in GlancePlus C.03.35.00.
glance Adviser memory consumption increases continually
Issue GlancePlus’s glance Adviser leaks memory when running continuously. Adviser
is used by the WLM data collectors glance_app, glance_gbl, glance_prm,
glance_prm_byvg, and glance_tt.
Workaround This memory leak is fixed in GlancePlus C.03.35.00.
WLM enables/disables SLOs at end of interval
Issue WLM enables and disables time-based SLOs only at the end of an interval. This
interval is 60 seconds by default and can be changed with the wlm_interval
keyword in your configuration file.
SLOs are time-based when you set their condition or exception keyword
values in the configuration file.
If your interval is too long, an SLO may not be enabled as indicated in the
configuration. For example, assume the interval is 1800 seconds (30 minutes).
Also assume that one SLO is supposed to have the entire system to itself for a
short period of time, with WLM enabling that one SLO for 20 minutes while
disabling all other SLOs for the same 20 minutes. If these 20 minutes begin at
3pm everyday, but the interval ends at 3:15pm, your configuration does not
actually go into effect until 3:15pm. Moreover, it is not changed again until
3:45pm.
Workaround Be aware of how your interval and time-based SLOs interact and adjust them
accordingly.
No metrics on startup or reconfiguration
Issue Metrics have no value on WLM startup or reconfiguration. WLM cannot work
toward any SLOs without metrics.
Workaround Data collectors should report metrics as soon after startup or reconfiguration as
possible.
WLM configurations cannot be activated with fewer than 100 Mbytes of
memory available
Issue When controlling memory, WLM allocates at least a minimum amount to each
group. If extended_shares is enabled, this minimum is 0.2% of the available
memory; otherwise, it is 1%. (Available memory is the amount reported by
prmavail; it is the amount that is not reserved for the kernel (/stand/vmunix)
and its data structures and for nonkernel system processes. Thus, available memory
is not the total memory on the system. Available memory varies over time. For
more information, see the Process Resource Manager User’s Guide.) WLM requires
that this minimum represent at least 1 Mbyte of memory. Thus, when memory
control is used, the system should have at least 100 Mbytes of available memory,
or at least 500 Mbytes if extended_shares is enabled.
GlancePlus may not correctly identify processes’ PRM groups 11