HP-UX Workload Manager A.03.05.xx Release Notes for HP-UX 11i v3 (B8843-90051, February 2011)

Configuration wizard requires PRM
Issue Starting with the WLM A.03.01 release, WLM no longer includes Process
Resource Manager (B3835DA). The WLM configuration wizard requires PRM
however. Without PRM installed, the wizard:
• Always sets the initial CPU (core) count to 1 in the pop-up dialog that
appears before the wizard itself appears
• Returns a message about the PRM API not being installed when it attempts
to validate a configuration
Workaround Install PRM A.03.00 or later.
Processes in transient FSS groups appear unexpectedly in other workload
groups
Issue
A deployed WLM configuration that has transient_groups set to 1 and
contains FSS transient group candidates from time-to-time contains an FSS
group called _IDLE_. As needed, WLM moves the jobs of the transient groups
to _IDLE_, where they get the minimum of CPU and memory resources. The
internal identifier for group _IDLE_ is picked by WLM on the fly (taken from
the pool of unused identifiers).
On a redeployment, if the new configuration contains an FSS group that happens
to have the identifier WLM selected for the _IDLE_ group in the deployment
that is being replaced, jobs in the _IDLE_ group will migrate to the FSS group
having the same identifier.
The same issue can arise going from:
• A transient deployment to another transient deployment
• A transient deployment to a non-transient deployment
Workaround
You can prevent this situation by using the -i option to wlmd when deploying
or redeploying a configuration. First, shut down wlmd (using the -k option),
then restart it using the -i option.
Modifying a managed partition requires WLM and the global arbiter be
stopped
Issue
Do not adjust any WLM-managed partition while wlmpard is running. This
includes using vparmodify, icapmodify, or icod_modify to change the
name, configuration, or resources (CPU and memory) associated with the virtual
partition or nPartition (and this also includes using parolrad to modify a cell
in a WLM-managed partition, as noted in “Performing online cell operations”
(page 20)).
Workaround
To adjust a partition, you must first shut down WLM—including wlmpard—on
all partitions that will be affected by the modification, modify the partition, and
then restart WLM. Changes to Instant Capacity (iCAP) affect the entire complex;
changes to a virtual partition affect the nPartition only, unless Instant Capacity
is configured on the nPartition. For example, if WLM is managing two virtual
partitions vParA and vParB, and you need to migrate memory resources from
vParA to vParB, you must shut down WLM in both virtual partitions. As another
example, to change the name of an nPartition, you must first shut down WLM
in every operating system instance across the entire complex, because the name
Configuration wizard requires PRM 19