Workload management dispatcher behavior in multimember environments

On multimember Db2 instances, the dispatcher behaves in the following ways:

• The value of the wlm_disp_concur database manager configuration parameter applies to each host or LPAR. In multimember databases, the dispatch concurrency level specified by the wlm_disp_concur configuration parameter is applied across all of the members.
• For multimember databases, CPU limits are enforced on a per host or LPAR basis - when multiple members are used, each partition is allowed to use all of a specified CPU limit as long as the sum across all members is less than or equal to the CPU limit. If the CPU limit on the single service class A is 35% and there are 2 members, then member 1 can use up to 35% if the sum of the CPU utilization across member 1 and 2 does not exceed 35%.

  

The workload management dispatcher supports micropartition environments in AIX. In micropartition environments, the percentage CPU utilization for both controls and monitoring in the workload management dispatcher is computed relative to the CPU resources allocated to the LPAR by the operating system or hypervisor over the most recent dispatcher CPU resource scheduling cycle, using the entitled (guaranteed) CPU resources for the LPAR as a baseline level. In cases when the CPU resource allocated to the LPAR is greater than the entitled CPU resources, the dispatcher computes the CPU utilization relative to the greater amount, and when the CPU resource allocation is less than the entitled CPU resources, the dispatcher computes the CPU utilization relative to the entitled CPU resources.