Interactions between profiles for monitoring threads and connections
When multiple profiles specify overlapping criteria, Db2® might apply such profiles in combination. However, Db2 might also apply one profile and exclude others, depending on the overlapping criteria.
Filtering scopes for monitoring threads and connections
| 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:
|
Precedence of profiles for threads and connections
- When multiple criteria are specified in the same category in different matching profiles,
Db2 uses only the profile that defines the
criterion that takes precedence in that category:
- ROLE takes precedence over AUTHID.
- COLLID takes precedence over PKGNAME.
- When separate matching profiles specify different numbers of criteria from the same category, the more specifically defined profile is used. For example, when one profile specifies both ROLE and AUTHID, and another specifies only ROLE, Db2 uses only the profile that specifies both criteria.
- When criteria from different categories are specified in separate profiles, Db2 uses all of the profiles in combination.
- When a profile is defined that uses asterisk (*) values for filter criteria and other profiles define specific values, Db2 uses only the profile that specifies the specific values.
- If two or more profiles from the same category specify the same exactly matching filtering criteria, only the profile with the newer timestamp is applied.
Order of profile evaluation for threads and connections
- IP address or domain name, in the LOCATION column.
- Product identifier, in the PRDID column.
- Role and authorization identifier, in both ROLE and AUTHID columns.
- Role, in the ROLE column only.
- Authorization identifier, in the AUTHID column only.
- Server location name, location alias, or database name, in the LOCATION column.
The location name of a
requester, for monitored threads from a Db2 for z/OS® requester.
- Collection identifier and package name, in both COLLID and PKGNAME columns.
- Collection identifier, in the COLLID column only.
- Package name, in the PKGNAME column only.
- Client application name, in the CLIENT_APPLNAME column.
- Client user identifier, in the CLIENT_USERID column.
- Client workstation name, in the CLIENT_WRKSTNNAME column.
Any profile that specifies a specific
value in a particular column has precedence over a profile that specifies a single-byte asterisk
value ('*') in the same
column.