HP-UX Workload Manager User's Guide

Integration with other products
Integrating with Serviceguard
Appendix D418
workload groups with inactive SLOs receive a minimum of 0.2% of
the total CPU resources (with incremental allocations of 0.1%).
Similarly, if you are using WLM memory management, the workload
group with no active SLOs receives 1% of the memory (0.2% if
extended_shares is set, with incremental allocations of 0.1%), unless
the group has a gminmem value requesting more. However, note that
groups associated with a process map always remain active even if
they have no associated active SLOs.
If you would prefer these groups to go away temporarily (as long as
they have no active SLOs) and consume no CPU or memory resources,
set the transient_groups tunable to 1 in a global tune structure:
tune {
transient_groups = 1;
}
With the transient_groups keyword set to 1, FSS groups with no
active SLOs are temporarily removed and therefore use no resources;
the minimum CPU allocation for PSET groups becomes 0 (or the
value for gmincpu, if it is defined and such resources are available).
Note that workload groups associated with a process map always
remain active.
If an FSS workload group has been temporarily removed, its gmincpu
and gminmem values (if any) are ignored.
If you prefer that these groups not be removed, leave
transient_groups disabled and enable the extended_shares
tunable instead. In addition, make sure the absolute_cpu_units
tunable is enabled. The extended_shares tunable significantly
reduces the minimum allocations of resources to groups.
NOTE The OTHERS workload is never removed—regardless of how many
active SLOs it has.
Step 3. Validate the syntax of the configuration file:
# /opt/wlm/bin/wlmd -c configfile
Correct any errors that are found.
Step 4. Distribute the WLM configuration file to all the nodes in the cluster.