Configuring limits for resource groups
By controlling the number of concurrent plans, you can help to improve performance for the active plans and avoid situations in which too many active plans result in inadequate performance for all of them.
To control the number of actively running plans associated with
a particular resource group, create a limiting scheduler rule for
that resource group. For example:
IF RESOURCEGROUP IS public THEN LIMIT 2The JOB MAXIMUM attribute of a resource group also controls the
number of actively running plans that are submitted by that group,
but this attribute is deprecated. The JOB MAXIMUM attribute can have
the following values:
- A value of 0 (or OFF) specifies that the group has no maximum for the number of concurrent plans. The group is restricted by the usual system settings and controls for concurrent plans.
- A value of 1 - 48 to set the job maximum to the specified integer value.
- A value of -1 (or AUTOMATIC) specifies that the system calculates a job maximum value that is based on the group's resource minimum multiplied by the number of GRA scheduler slots (default 48). For example, if a group has a resource minimum of 20%, the job maximum is (.20 * 48) or approximately 9.