Threshold domain and enforcement scope
Each threshold operates on a domain. Only activities taking place in the domain of a threshold can be affected by that threshold.
- Database
- Service superclass
- Service subclass
- Work action
- Workload
- Statement
Within each of these threshold domains, a threshold has a scope over which it is enforceable, such as a single workload occurrence, a member, the execution of a specific statement, or all members. This is known as the enforcement scope of the threshold. For example: Service class aggregate thresholds can have one of two enforcement scopes: database and member. An example of an aggregate threshold that applies only at the member level is the maximum number of concurrent connections for a service superclass on a member (TOTALSCMEMBERCONNECTIONS). Similarly, the following table shows that you can specify the processor time threshold (CPUTIME) at the database, superclass, subclass, work action or workload domain and that it is enforced per member. That is, the upper boundary specifies the maximum amount of user and system processor time per member that an activity may use.
Threshold domain | Thresholds with database enforcement scope | Thresholds with member enforcement scope | Thresholds with workload occurrence enforcement scope |
---|---|---|---|
Database |
|
Not applicable | |
Work action |
|
Not applicable | |
Service superclass |
|
Not applicable | |
Service subclass |
|
Not applicable | |
Workload |
|
||
Statement |
|
Not applicable | |
1 Database enforcement scope is only allowed in environments other than Db2 pureScale® environments. In a Db2 pureScale environment, only member enforcement scope is allowed. |