PTF Cover Letter
PTF ( Program Temporary Fixes ) Cover letter
OSP-Workload Capping function
Pre/Co-Requisite PTF / Fix List
REQ LICENSED PTF/FIX LEVEL
TYPE PROGRAM REL NUMBER MIN/MAX OPTION
---- -------- --- ------- ------- ------
DIST 5770SS1 710 SI39790 00/00 0000
DIST 5770SS1 710 SI40276 00/00 0000
DIST 5770SS1 710 SI39786 00/00 0000
DIST 5770SS1 710 SI39787 00/00 0000
DIST 5770SS1 710 SI39782 00/00 0000
DIST 5770SS1 710 SI40733 00/00 0000
DIST 5770SS1 710 SI39791 00/00 0000
DIST 5770SS1 710 SI39771 00/00 0000
DIST 5770999 710 MF50758 00/00 0000
Application of this PTF may disable or render ineffective programs that
use system memory addresses not generated by the IBM translator,
including programs that circumvent control technology designed to limit
interactive capacity to purchased levels. This PTF may be a prerequisite
for future PTFs. By applying this PTF you authorize and agree to the
This PTF is subject to the terms of the license agreement which
accompanied, or was contained in, the Program for which you are obtaining
the PTF. You are not authorized to install or use the PTF except as part
of a Program for which you have a valid Proof of Entitlement.
SUBJECT TO ANY WARRANTIES WHICH CAN NOT BE EXCLUDED OR EXCEPT AS EXPLICITLY
AGREED TO IN THE APPLICABLE LICENSE AGREEMENT OR AN APPLICABLE SUPPORT
AGREEMENT, IBM MAKES NO WARRANTIES OR CONDITIONS EITHER EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON INFRINGEMENT,
REGARDING THE PTF.
The applicable license agreement may have been provided to you in printed
form and/or may be viewed using the Work with Software Agreements (WRKSFWAGR)
APAR Error Description / Circumvention
This PTF, along with the requisite PTFs, provides the
infrastructure and user interface needed for Workload Capping.
The workload capping function can be used to limit the
processing capacity of a workload to a subset of processor cores
in a partition. A workload capping group can be created with a
limit on the number of processor cores. Jobs can then be
assigned to the workload capping group. The system enforces this
processing core assignment by ensuring that any job and its
associated threads cannot run on more processor cores then have
been designated by the workload capping group.
CORRECTION FOR APAR 'SE43311' :
The following instructions can be used to set up workload
capping in a partition. Additional information about workload
capping including commands, APIs, performance tools and license
management can be found in the IBM i Information Center under
the various topics at
A workload capping 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 capping group to define the license term and feature of
the product in the group. To set up workload capping, use the
1.Add a workload capping group using the Add Workload Capping
Group (ADDWLCGRP) command. The workload capping 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 capping group can run on concurrently.
For example: ADDWLCGRP WLCGRP(MYGROUP) PRCLMT(2)
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 capping group.
For example: ADDWLCPRDE WLCGRP(MYGROUP) PRDID(5770xxx)
3.Create a special data area named QWTWLCGRP that defines which
subsystems use which workload capping group using the Create
Data Area (CRTDTAARA) command. The data area must be TYPE(*CHAR)
and the library name must be QSYS. The data area length must be
at least 20 characters long, and contain pairs of subsystem and
workload capping group names. Each name is 10 characters in
length, left-justified, and padded with blanks.
For example: CRTDTAARA DTAARA(QSYS/QWTWLCGRP) TYPE(*CHAR)
LEN(2000) VALUE('MYQBATCH WLCGRP01 MYSBSNAME MYGROUP ')
TEXT('Subsystems to use workload capping') AUT(*USE)
4.Use the Display Data Area (DSPDTAARA) command to verify that
the correct number of spaces have been used. Ensure the names
start at positions 1, 11, 21, and so on. If a subsystem name or
workload capping group name is 10 characters long, there can be
no space between that name and the beginning of the next name.
For example: DSPDTAARA DTAARA(QSYS/QWTWLCGRP)
5.Start the subsystems that are defined in the data area created
using the Start Subsystem (STRSBS) command. The data area can be
created or changed while the subsystem is active, but has no
effect until the subsystem is ended and restarted.
For example: STRSBS SBSD(QGPL/MYSBSNAME)
Note: Verify that a CPI146C message (Subsystem &1 is using
workload capping group &2) is logged in the subsystem job log
when the subsystem was started. Jobs that start in subsystem
MYSBSNAME are now limited to two processor cores, as defined by
the workload capping group named MYGROUP.
6.To change the workload capping group for a job after it has
already started, use the Change Job (CHGJOB) command or the
Change Job (QWTCHGJB) API. The job does not need to be running
in a subsystem that has a workload capping group defined.
For example: CHGJOB JOB(123456/QUSER/MYSERVER) WLCGRP(MYGROUP)
7.To change the processing capacity for a group, use the Change
Workload Capping Group (CHGWLCGRP) command. The processor limit
can be changed while jobs using the workload capping group are
For example: CHGWLCGRP WLCGRP(MYGROUP) PRCLMT(4)
- The workload capping group and QWTWLCGRP data area can be
created while the subsystem is active. This has no effect on the
jobs in that subsystem until the subsystem is ended and
- The Remove Workload Capping Group (RMVWLCGRP) command can be
used to change all jobs actively running in a workload capping
group to no longer be assigned to that group.
- If you remove a workload capping 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
capping group. They continue to use all processor cores
- The controlling subsystem (as defined by QCTLSBSD system
value) cannot use a workload capping group.
- Batch immediate jobs are started using the workload capping
group used by the job that starts them (parent job).
- Up to 255 workload capping groups can be created for the
current system or logical partition.
- Changes to the number of processor cores for a workload
capping group take effect immediately.
For more information see the Work management topic in the IBM i
7.1 Information Center.
CIRCUMVENTION FOR APAR 'SE43311' :
THIS PTF CAN BE APPLIED IMMEDIATE OR DELAYED.
PTF/FIX NO(S). APAR TITLE LINE
|APAR Fixed..........................||View details for APAR SE43311|
|Superseded by:......................||View fix details for PTF SI57866|
|MRI Feature ........................||NONE|
13 September 2010