When a Workload Policy contains two or more rules of the same type (either JOB or RESOURCE) that are associated with the same Load-Index, but differ in the defined limit (of jobs or resources) and threshold load level, the order of rules within the Workload Policy determines the order in which the defined limitations take effect.

In general, the limitation from the first rule that meets the specified Load-Index level criteria is enforced. Therefore, for all your rules to be applied, ensure that the most severe level limitation appears first in the Workload Policy.

For example:

• In Workload Policy WP1, the first rule includes the following line for limiting jobs:

LIMIT 0000  WHEN LOAD-INDEX LPAR5              AT LEVEL CRITICAL  AND ABOVE

And the second rule includes the following line:

LIMIT 0005  WHEN LOAD-INDEX LPAR5              AT LEVEL HIGH      AND ABOVE

In this case, when the load level reaches CRITICAL, no jobs can run. When the load level is at HIGH or V-HIGH, 5 jobs are allowed to run.

• In Workload Policy WP2, the rules are reversed. The first rule includes the following line:

LIMIT 0005  WHEN LOAD-INDEX LPAR5              AT LEVEL HIGH      AND ABOVE

And the second rule includes the following line:

LIMIT 0000  WHEN LOAD-INDEX LPAR5              AT LEVEL CRITICAL  AND ABOVE

In this case, when the load level reaches HIGH, V-HIGH, or CRITICAL, 5 jobs are allowed to run. The second rule is ignored, as the criteria that it defines are already met by the first rule.