DB2 Version 9.7 for Linux, UNIX, and Windows

FP1: Work action sets can be defined at workload level

Starting with Version 9.7 Fix Pack 1, you can define work action sets at the workload level to control activities submitted by occurrences of those workloads, based on the type and size of work. The option to control work at the workload level complements the control options already available at the service superclass and database levels. A work action set, defined on a workload definition, applies to all work submitted by connections that are currently mapped to that workload definition.

With the ability to define work action sets at the workload level, you can monitor and control activities submitted by a specific application without having to map those activities to a distinct service class. Control of incoming work includes the application of activity thresholds to activities submitted by occurrences of the workload, as well as the ability to introduce a concurrency threshold on some or all of that same work.

The following list contains the types of work actions that are available when a work action set is applied at the workload level:

COUNT ACTIVITY
PREVENT EXECUTION
COLLECT ACTIVITY DATA
COLLECT AGGREGATE ACTIVITY DATA
Thresholds that apply to each individual activity in the matching work class:
- ESTIMATEDSQLCOST
- SQLROWSRETURNED
- ACTIVITYTOTALTIME
- SQLTEMPSPACE
- SQLROWSREAD
- CPUTIME
CONCURRENTDBCOORDACTIVITIES threshold that applies to all activities as a group in the matching work class. This threshold controls the number of concurrent activities in the matching work class from all occurrences of the workload.