HP-UX Workload Manager A.03.02.xx Release Notes for HP-UX 11i v1, HP-UX 11i v2, and HP-UX 11i v3

HP-UX Workload Manager Release Notes

Compatibility information and installation requirements

Compatibility with PRM

As of version A.03.01, WLM no longer includes PRM in the bundle. As a result, upgrading

WLM no longer triggers a reboot.

WLM will run only with PRM C.03.00 or later. If PRM C.03.00 or later is already on the

machine where you are installing or upgrading WLM, you can continue to manage FSS and

PSET-based workload groups just as if PRM had been installed with WLM.

If you are installing WLM for the first time on a machine, you can only use a strictly

host-based configuration—a configuration that does not include a prm structure and is

designed exclusively for moving cores across HP-UX Virtual Partitions or nPartitions, or for

activating Temporary Instant Capacity (TiCAP) or Pay per use (PPU) cores. To manage FSS

and PSET-based workload groups, you must install PRM separately. With your purchase of

WLM, you are entitled to a PRM license. For information on receiving the PRM license,

contact your regional licensing service organization.

When the Servicecontrol Manager (SCM) bundle is built during the WLM installation, it will

include the PRM API only if PRM is already installed. The SCM integration bundle will not be

able to validate PRM-based configurations without the PRM API.

NOTE If you plan to use the WLM configuration wizard, install the appropriate

version of PRM. To take advantage of the latest updates to WLM, use the latest

version of PRM (C.03.02 or later).

To ensure that WLM works properly on a system with PRM C.03.02 or later,

upgrade WLM to A.03.02 or later. When upgrading WLM A.03.00 or earlier,

upgrade WLM prior to upgrading PRM.

You can use WLM to control resources managed by PRM. WLM uses PRM when a prm

structure is included in the WLM configuration. With such configurations, you can use PRM’s

informational and monitoring commands such as prmlist and prmmonitor. You can also use

the prmrun and prmmove commands, among others. If you use the prmconfig command,

invoke it with no options or the -u (unlock) option—do not use the -r (reset) option.

Ordinarily, WLM and PRM should not be used to manage resources on the same system at the

same time. Using both WLM and PRM to control resources at the same time might cause

inconsistent behavior and undesirable performance. However, you can use both products at

the same time if the PRM configuration uses FSS groups only (no PSET-based groups) and the

WLM configuration is strictly host-based. (A strictly host-based configuration is one that does

not include a prm structure; it is designed exclusively for moving cores across HP-UX Virtual

Partitions or nPartitions, or for activating Temporary Instant Capacity (TiCAP) cores or Pay

per use (PPU) cores.) You might want to use both products to take advantage of certain

features of PRM that are not included with the latest release of WLM, such as PRM’s