A change in a resource quantity in the database is not also implemented in the plan after JnextPlan

You make changes to the number of available resources in the database, but the number of available resources in the plan does not change. The global option enCFResourceQuantity is set to no.

Cause and solution:

If the global option enCFResourceQuantity is set to yes, you would expect that any changes to the available quantity of a given resource in the database would not be implemented in the plan, provided there is at least one job or Job Scheduler instance using that resource in the extended plan.

Similarly, if the global option enCFResourceQuantity is set to no you might expect that the available resource quantity would change after JnextPlan. However, this is not always true, depending on the quantity of that resource being used by jobs and Job Scheduler instances currently in the plan:
  • If the usage of the resource by jobs and Job Scheduler instances is less than or equal to the new total of available resources in the database, the available quantity of the resource is changed in the plan.
  • If the usage of the resource by jobs and Job Scheduler instances is greater than the new total of available resources in the database, the available quantity of the resource is not changed in the plan.
To be sure to update the quantity of resources in the plan, make available at least as many instances of the resource as are required by the jobs and Job Scheduler instances in the plan.

See also the description of the enCFResourceQuantity option in the IBM® Workload Scheduler: User's Guide and Reference.