HP-UX Workload Manager User's Guide

Understanding how PRM manages resources
Management of applications
Appendix F 459
How the application manager affects workload group
assignments
The PRM application manager checks that applications are running in
the correct workload groups every interval seconds. The default
interval is 30 seconds; however, you can change it with “prmconfig -I
interval APPL” as explained in prmconfig(1).
When determining the workload group assignment for a process
identified by multiple records, WLM gives precedence (from highest to
lowest) to the assignments as follows:
1. Process maps
2. Compartment records
3. Application records
4. User records
5. Unix group records
Thus, if a PID specified by a PID_finder script defined in a process map
matches a compartment, application, user, or Unix group record, the
process map determines the placement of the process.
A process may start in a workload group other than its assigned group
because it inherits the group of the process that started it. However,
WLM will eventually move the process to the workload group specified in
its record. For information on process placement for inactive FSS groups
and PSET-based groups, see “Temporarily removing groups with inactive
SLOs (optional)” on page 220
If you use the prmmove or prmrun command to place a process in a
workload group, that assignment takes precedence over any of the
assignments defined by the WLM records or process maps.
To determine where to place a process, the application manager checks
for the following:
1. Did a user manually move (using prmrun or prmmove) the process to
the current workload group, or was the process moved to the current
workload group by a process map?
If yes, leave the process where it is.
If no, continue with the checklist.