Profiles for monitoring and controlling Db2 for z/OS® subsystems
A profile is a set of criteria that identifies a particular context on a Db2® subsystem. Examples include threads, connections, or SQL statements that have particular attributes.
If
the value of the PROFILE_AUTOSTART subsystem parameter is set to YES, the START PROFILE command is
issued automatically as part of Db2 start
processing.
Overview of uses for profiles
- Monitoring threads and connections
- Setting or disabling certain subsystem parameters for particular SQL statements
- Specifying subsystem properties when modeling a production environment on a test system
- Setting thresholds for query acceleration
Evaluating a dynamic SQL query for acceleration
Setting the value of a special
register
Many of these actions are not closely related. The rules for how to define the scope of the profile depend on the action that the profile defines. Certain combinations of filtering columns are either required or accepted only for certain KEYWORDS values. The following table summarized these relationships. For detailed information about the accepted filtering columns and KEYWORDS values, see the specific information for each action.
| Profile action | Applicable filtering columns | Applicable KEYWORDS values |
|---|---|---|
Monitoring the use of system resources by remote
applications, including remote threads and connections 1![]() |
Any of the following combinations with particular rules for certain
KEYWORDS values:
|
|
| Setting or disabling optimization parameters for SQL statements | All
of the following columns:
|
|
| Modeling a production system on a test system | None. Profiles for this purpose have a global scope on the test subsystem. |
|
| Setting thresholds for query acceleration | Contact IBM® Support for the accelerator product. |
|
Evaluating a dynamic SQL query for
acceleration![]() |
Supported by profiles with a global scope and those with the following combinations:
![]() |
ACCEL_NAME_EXPLAIN![]() |
Setting the value of a special register for remote applications
1![]() ![]() |
Any of the following combinations with particular rules for certain
KEYWORDS values:
![]() |
SPECIAL_REGISTER![]() |
Profiles of this type apply only to remote applications.
The scope of a profile
The scope of a profile, the defined context in which Db2 applies the actions specified by the profile, are stored as rows in the SYSIBM.DSN_PROFILE_TABLE table. Rows in the SYSIBM.DSN_PROFILE_ATTRIBUTES table control the actions that Db2 applies when a process meets the criteria defined by the profile. The values of the PROFILEID columns of each table associate each profile with the corresponding actions for that profile. The PROFILE_ENABLED column indicates whether Db2 activates the profile when you start monitoring.
- AUTHID
- COLLID
- LOCATION
- PKGNAME
- PLANNAME
- PRDID
- ROLE
- CLIENT_APPLNAME
- CLIENT_USERID
- CLIENT_WRKSTNNAME
For profiles that specify values for optimizing subsystem parameters, the following table shows combinations of criteria that create valid profiles. Other combinations are not valid.
| Filtering category | Columns to specify |
|---|---|
| Collection identifier and package name | Specify all of the following columns:
|
For profiles that define contexts for the use of system resources by threads and connections, the following combinations of criteria create valid profiles. Other combinations are not valid.
| Filtering category | Columns to specify |
|---|---|
| Client IP address or domain name | Specify only the LOCATION column. The value can be an IP address or
domain name. This category is the only accepted filtering criteria for profiles that specify the MONITOR CONNECTIONS. |
| Client product identifier | Specify only the PRDID column. |
| Role or authorization identifier | Specify one or all of the following columns:
Profiles that specify both ROLE and AUTHID take precedence over profiles that specify only one value. Profiles that specify only ROLE take precedence over profiles that specify only AUTHID |
| Collection identifier or package name | Specify only one or all of the following columns:
Profiles that specify both COLLID and PKGNAME take precedence over profiles that specify only one value. Profiles that specify only COLLID take precedence over profiles that specify only PKGNAME |
| Location name, or location alias | Specify only the location name or location alias in LOCATION column.
This category applies only to profiles that specify MONITOR THREADS and MONITOR IDLE THREADS. |
| Client application name, user ID, or workstation ID. | Specify only
one of the following columns:
|