CPUTIMEINSC threshold
The in-service-class CPUTIMEINSC threshold specifies the maximum amount of combined user and system processor time that an activity may use on a particular member while running in a specific service subclass. Use this threshold to detect and control activities that are using excessive processor resources.
- Class
- Activity
- Definition domain
- Service subclass
- Enforcement scope
- Member
- Tracked work
- See the information later in this topic
- Queuing
- No
- Unit
- Time
- Predictive or reactive
- Reactive
The processor time that an activity spends running is measured from the time that the activity enters the current service subclass until the time that the activity leaves the service subclass or finishes running.
This threshold differs from the CPUTIME threshold in that it controls only the amount of processor time that may be used in a specific service subclass, not the total amount of processor time used during the lifetime of the activity.
Activities tracked by this threshold are as follows:
- All DML activities. This includes DML activities that originate from within IMPORT, EXPORT and other CLP commands.
- CALL activities. Note that the processor time for a CALL activity does not include the processor time of any child activity. The processor time spent in fenced processes is also not counted towards the total processor time for the CALL activity.
You can use the REMAP ACTIVITY action to control activities by remapping them to a service subclass with different resource assignments.
Examples
The following example creates two service subclasses, A1 and A2, under a superclass A, with a single in-service-class CPUTIMEINSC threshold that remaps activities between subclasses after 1 minute of processor time has been used during query evaluation in service subclass A1. An event monitor record is logged.
CREATE SERVICE CLASS A;
CREATE SERVICE CLASS A1 UNDER A;
CREATE SERVICE CLASS A2 UNDER A;
CREATE THRESHOLD T1 FOR SERVICE CLASS A1 UNDER A
ACTIVITIES ENFORCEMENT MEMBER
WHEN CPUTIMEINSC > 1 MINUTE CHECKING EVERY 30 SECONDS
REMAP ACTIVITY TO A2 LOG EVENT MONITOR RECORD;