HP-UX Workload Manager User's Guide

Understanding how PRM manages resources
Management of applications
Appendix F 461
If yes, move the process to the PRM_SYS group.
If no, the application manager continues with the checklist.
5. Is the process in the PRM_SYS group, or does it have a user ID
different from its parent?
If yes, continue with the checklist.
If no, leave the process where it is.
6. Is the process run by a user associated with a user record?
If yes, move the process to the initial group indicated in the user
record.
If no, continue with the checklist.
7. Does the effective group ID (GID) of the process match a Unix group
record?
If yes, move the process to the group indicated in the Unix group
record.
If no, move the process to the OTHERS group.
To illustrate these rules, consider the following application records:
apps = GroupA : /bin/call_home,
GroupB : “/bin/cal*”,
GroupC : /bin/cal,
GroupD : “/bin/c*”,
GroupE : /bin/call_home phone_home “tele*_home”,
GroupF : /opt/foo/bin/bar,
GroupG : /opt/foo/bin/bar_none,
GroupZ : /bin/call_home “*home”;
Assume a user starts an application, my_favorite_app, without using
prmrun:
% my_favorite_app
Because the application does not have an application record, it does not
meet any of the criteria discussed previously and starts in the invoking
user’s workload group.
Now assume the user starts the bar_none application, which has a
record, but is started in a group specified using prmrun.
% prmrun -g GroupA bar_none