Limiting resource usage by client information
You can limit the amount of processor resources that are used by a specific group of SQL statements based on the client information of the statements.
Before you begin
Provide client information to Db2 by using the appropriate application programming interface to set the values of the following special registers:
- CURRENT CLIENT_APPLNAME special register
- CURRENT CLIENT_USERID special register
- CURRENT CLIENT_WRKSTNNAME special register
This action is required only when the client application does not use the default values.
About this task
- Application name
- End-user ID
- Workstation ID
- IP address
The values for the client information that are found at the start of a new unit-of-work are used to determine which row of the RLMT table controls the processing of dynamic requests for the duration of the unit-of-work.
Resource limits apply only to the following types of SQL statements:
- SELECT
- INSERT
- UPDATE
- MERGE
- TRUNCATE
- DELETE
You can specify resource limits for dynamic SQL statements and static SQL statements. Resource limits apply to SQL statement regardless of whether they are issued locally or remotely. The resource limit facility does not apply to primary or secondary authorization IDs that have installation SYSADM or installation SYSOPR authority.
If both DSNRLMTxx and DSNRLSTxx tables exist, rows in the DSNRLMTxx table that match a statement take priority over any matching rows in the DSNRLSTxx table.
Procedure
To limit the use of resources for middleware servers:
Results
- Exact match
- Application name
- User ID
- Workstation name
- IP address
- No row match