HP-UX Workload Manager A.03.00 Release Notes for HP-UX 11i v1 and HP-UX 11i v2

HP-UX Workload Manager Release Notes
What’s in this version
8
• wlmpard is no longer required to be running in a partition on the managed complex
Previously, if WLM was managing the partitions in a complex, wlmpard had to be running
in one of those partitions. Now, wlmpard simply has to be running on a supported platform
with network connectivity to the managed partitions.
• Terminology change: The Instant Capacity on Demand (iCOD) product is now known as
Instant Capacity, or iCAP. Given WLM’s integration with this product, Instant Capacity is
mentioned in a number of places in the WLM product and documentation.
• Configuration file for wlmpard now has a utilitypri keyword
The utilitypri keyword allows you to specify the lowest priority at which WLM is
allowed to use Temporary Instant Capacity or Pay Per Use resources to meet service-level
objectives for your workloads.
The utilitypri keyword allows WLM—when Temporary Instant Capacity is
available—to adjust the CPU total to meet demand.
Using this keyword also ensures WLM maintains compliance with your license for
Temporary Instant Capacity: When the license is exhausted, WLM will no longer attempt
to use the temporary resources.
For more information, see the wlmparconf(4) man page.
• Configuration file for wlmpard no longer supports the partitions or weight keywords
If you use either the partitions or weight keywords in your wlmpard configuration file,
WLM issues warnings and ignores the keywords’ values.
You can still assign weights to workload groups in the wlmd configuration file. You can also
assign a weight on a host as a whole using the new hweight keyword in the wlmd
configuration.
For more information, see the wlmparconf(4) man page.
• The WLM GUI now has a Reconnect button that allows you to re-establish a
connection—without re-entering all the data—to a system you activated a configuration
on. After reconnecting, you can monitor your workloads.
• The recommended value for wlm_interval is 5 when using usage goals
Typically, you should set wlm_interval to 5 when your configuration includes a usage
goal.
• cntl_base_previous_req now set to 1 by default
In previous releases, the default value for cntl_base_previous_req was 0. The default
value is now 1.
For more information, see the wlmconf(4) man page.