HP-UX Workload Manager User's Guide

Integration with other products
Integrating with Serviceguard
Appendix D 417
c. Set up slo structures for each status metric, with the SLO being
active when the package is active:
slo pkgA_slo {
...
condition = metric pkgA_active;
...
}
slo pkgB_slo {
...
condition = metric pkgB_active;
...
}
Recall that the condition statement governs when an SLO is active:
If an SLO’s condition expression is true, the SLO is active. In these
cases, the expressions “metric pkgA_active” and
“metric pkgB_active” are true when the pkgA_active and
pkgB_active metrics are 1.
NOTE Workload groups that have only inactive SLOs continue to consume
system resources. To prevent this needless consumption, use the
transient_groups tunable, which is described in Step e.
d. (Optional) Use absolute_cpu_units in a global tune structure to
ensure that WLM treats 100 CPU shares as one core. For example,
use it in the configuration if the SLO for pkgA is requesting 200
shares, which must be treated as two cores. Set this tunable as
shown:
tune {
absolute_cpu_units = 1;
}
e. (Optional) Use transient_groups in a global tune structure to
temporarily remove workload groups with no active SLOs.
By default, if a package’s workload group has no active SLOs, WLM
reduces its resource shares. Such a workload group receives a
minimum of 1% of the total CPU resources (for FSS groups) or one
core (for PSET-based groups), unless it has a gmincpu value
requesting more. If the tunable extended_shares is set to 1, FSS