Setting up workload groups

A workload group defines the number of processor cores that can be used concurrently by jobs and threads that are associated with the group. Product entries can be added to a workload group to define the license term and feature of the product in the group. To set up workload groups, use the character-based interface.

  1. Add a workload group using the Add Workload Group (ADDWLCGRP) command. The workload group can be added with any name you choose. The processor limit defines the number of cores that jobs and threads associated with this workload group can run on concurrently.
  2. Add product information to the group using the Add WLC Product Entry (ADDWLCPRDE) command. Product entries define the license term and feature of the product that is limited by the number of processor cores defined for the workload group. See Setting up software licensing with workload groups for more information on setting up software licensing with workload groups.
  3. Start of changeAdd the workload group name to the subsystem description.
    End of change
  4. Start of changeStart the subsystem using the Start Subsystem (STRSBS) command. The workload group name can be changed while the subsystem is active, but has no effect on the jobs that are already active in that subsystem.
    Note: A CPI146C message (Subsystem &1 is using workload group &2) is logged in the subsystem job log when the subsystem is started. Jobs that start in subsystem MYSBSNAME are now limited to two processor cores, as defined by the workload group named “MYGROUP”.
    End of change
  5. To change the workload group for a job after it has already started, use the Change Job (CHGJOB) command. The job does not need to be running in a subsystem that has a workload group defined.
  6. To change the processing capacity for a group, use the Change Workload Group (CHGWLCGRP) command. The processor limit can be changed while jobs using the workload group are active.
  • The Remove Workload Group (RMVWLCGRP) command can be used to change all jobs actively running in a workload group to no longer be assigned to that group.
  • If you remove a workload group (RMVWLCGRP) while a subsystem that is using it is active, new jobs that are started are not limited.
  • System jobs and subsystem jobs do not run in a workload group. They continue to use all processor cores available.
  • The controlling subsystem (as defined by QCTLSBSD system value) cannot use a workload group.
  • Batch immediate jobs are started using the workload group used by the job that starts them (parent job).
  • Up to 255 workload groups can be created for the current system or logical partition.
  • Changes to the number of processor cores for a workload group take effect immediately.