HP-UX Workload Manager User's Guide

WLM quick start: the essentials for using WLM
How to put an application under WLM control
Chapter 284
curly : coders surfers,
larry : testers surfers;
}
Besides the default OTHERS group, this example has three groups of
users: testers, coders, and surfers. The user records cause processes
started by users moe and curly to be run in group coders by default, and
user larry’s processes to be run in group testers by default. Each user is
also given permission to run jobs in group surfers if they wish, using
the prmrun or prmmove commands mentioned in sections to follow. Users
not belonging to any of the specified groups are placed in OTHERS by
default. For more information on setting up user records, see “Assigning
users and user access to workload groups (optional)” on page 164.
Unix group records: Workload separation by Unix
group ID
You can place processes in workload groups according to the Unix groups
the processes run in. You specify your Unix group-workload group
mapping in the uxgrp statement. Here is an example:
prm {
groups = OTHERS : 1,
testers : 2,
coders : 3,
surfers : 4;
uxgrp = sports : surfers,
shoes : coders,
appliances : testers;
}
Besides the default OTHERS group, this example has the three workload
groups testers, coders, and surfers. The Unix group records cause
processes running in Unix group sports to be placed in workload group
surfers, while processes running in Unix group shoes are placed in
workload group coders, and processes in Unix group appliances are
placed in workload group testers. Processes not running in any of the
specified Unix groups are placed in OTHERS by default.
WLM supports Unix group records only if PRM C.03.02 or later is
running on the system. For more information on setting up Unix group
records, see “Assigning Unix groups to workload groups (optional)” on
page 165.