HP Process Resource Manager User's Guide

Understanding how PRM manages resources
How PRM controls resources
Chapter 242
NOTE Application records must assign applications only to leaf groups—not
parent groups. Similarly, user records must assign users only to leaf
groups. For more information on these record types, see “Controlling
applications” on page 126 and “Specifying PRM users” on page 139.
In group/CPU records, each PRM group—regardless of where it is in the
hierarchy—must be assigned resource shares.
Hierarchies offer a number of advantages, as explained below:
• Facilitates less intrusive changes—Similar to how shares in a flat
configuration allow you to alter one record while leaving all the
others alone, hierarchies enable you to alter the hierarchy in one
area, leaving the rest unchanged.
• Enables you to use a configuration template—Create a configuration
file that provides each department access to the system, then
distribute the configuration and assign resources giving preference
to certain departments on different machines.
• Allows continued use of percentages—If you prefer using
percentages instead of shares, you can assign each level in the
hierarchy only 100 resource shares.
• Facilitates giving equal access—If you want each PRM group to have
equal access to a resource, simply assign each group the same
number of shares. When you add a group, you do not have to
recalculate resources and divide by the new number of groups; just
assign the new group the same number of shares as the other groups.
Similarly, removing a group does not require a recalculation of
resources; just remove the group.
• Allows for more intuitive groups—Hierarchies enable you to place
similar items together, such as all databases or a business
entity/goal, and assign them resources as a single item.