HP-UX Workload Manager User's Guide

Understanding how PRM manages resources
Management of applications
Appendix F458
db02_payroll
db03_payroll
db04_payroll
dbsmon_payroll
dbwr_payroll
dbreco_payroll
To make sure all payroll processes are put in the same workload group,
use pattern matching in the alternate names field of the application
record, as shown in the following example:
apps = business_apps : “/usr/bin/database db*payroll”;
For alternate names and pattern matching to work, the processes must
share the same file ID. (The file ID is based on the file system device and
the file’s inode number.) PRM performs this check to make sure that only
processes associated with the application named in the application
record are put in a configured workload group.
If there are multiple application records with alternate names that
match an application name due to redundant pattern matching
resolutions, the first record to match the application name takes
precedence. For example, the application abb matches both of the
following application records:
apps = GroupA : /opt/foo/bin/bar “a*”,
GroupB : /opt/foo/bin/bar “*b”;
Because the *b record is first (based on ASCII dictionary order), the
application abb would be assigned to the workload group GroupB.
Note that Extended Regular Expression alternate names are matched
against the entire available command line, while non-ERE alternate
names are matched against non-dash command-line arguments only.
Note also that commas within an ERE are not separators for alternate
names; they must match commas in the command line.
Knowing the names of all the processes spawned and renamed by the
applications can help in creating pattern matching that is only as
general as it needs to be. Eliminate redundant name resolutions
whenever possible, and make sure pattern matching does not cause
unwarranted moves.
For information on how alternate name pattern matching affects
precedence, see the next section.