DSN_PROFILE_TABLE profile table
Each row in the profile table, DSN_PROFILE_TABLE, defines a profile. A system profile is a set of criteria that identifies a specific context on a Db2 subsystem. Examples include threads, connections, or SQL statements that have certain attributes. The schema is SYSIBM.
Profile tables identify contexts in which Db2 takes particular actions such as resource monitoring, subsystem parameter customization, and dynamic SQL stabilization. The contexts might identify statements, threads, or connections that are based on information about the originating application, system, or user. For an overview of how to use profile tables and a summary of the specific uses for profile tables, see Monitoring and controlling Db2 with profile tables.
The profile tables and related indexes are created when you run job DSNTIJSG during Db2 installation, as described in Job DSNTIJSG.
The following table describes the columns in SYSIBM.DSN_PROFILE_TABLE.
| Column name | Data type | Description |
|---|---|---|
| AUTHID | VARCHAR(128) | The authorization ID of a monitored user. For profiles that monitor system resources, this value is optional if a value for ROLE is specified. This value must be null if values are specified for COLLID, PKGNAME, LOCATION, or PRDID. You can use an asterisk (*) wildcard in this column to specify that multiple values match the criteria for this profile. However, for any thread or connection that matches multiple profiles, Db2 applies only the single most specific profile, in the following order of precedence:
![]() For example, if the column value is 'TEMP*', then any authorization ID which begins with TEMP (and including TEMP by itself), would match this profile specification. |
| PLANNAME | VARCHAR(24) | The name of a plan. This value must be null if values are specified for AUTHID, LOCATION, ROLE, PKGNAME, or PRDID columns for monitoring system resources. |
| COLLID | VARCHAR(128) | A collection identifier of a monitored collection. For profiles that monitor system resources, this value is optional if the value of PKGNAME is specified, and this value must be null if values are specified for AUTHID, LOCATION, ROLE, or PRDID. For other types of profiles, this column is required when PKGNAME is specified. You can use a single-byte asterisk value ('*') in this column to specify that the profile matches all connections or threads that connect to the Db2 subsystem. However, for any thread or connection that matches multiple profiles, Db2 applies only the single most specific profile, in the following order of precedence:
When an asterisk is used, the specified limit applies separately to the number of connections or threads allowed for each requester.![]() ![]() |
| PKGNAME | VARCHAR(128) | A package name of a monitored plan. This value is optional if a value for COLLID is specified. This value must be null if values are specified for AUTHID, LOCATION, ROLE, or PRDID You can use a single-byte asterisk value ('*') in this column to specify that the profile matches all connections or threads that connect to the Db2 subsystem. However, for any thread or connection that matches multiple profiles, Db2 applies only the single most specific profile, in the following order of precedence:
When an asterisk is used, the specified limit applies separately to the number of connections or threads allowed for each requester.![]() ![]() |
| LOCATION | VARCHAR(254) |
One of the following items:
The value is interpreted as a location name when the name string is less than or equal to 16 bytes and does not contain colon (:) or period (.) characters. When these characters are found, the value is checked for a valid IP address or a valid domain name. You can use a single-byte asterisk value ('*') in this column to specify that the profile matches all connections or threads that connect to the Db2 subsystem. However, for any thread or connection that matches multiple profiles, Db2 applies only the single most specific profile, in the following order of precedence:
When an asterisk is used, the specified limit applies separately to the number of connections or threads allowed for each requester.![]() ![]() |
| PROFILEID | INTEGER GENERATED BY DEFAULT AS IDENTITY PRIMARY KEY NOT NULL | The unique identifier for the profile that is defined by this row. |
| PROFILE_TIMESTAMP | TIMESTAMP NOT NULL WITH DEFAULT | The time when the row was inserted or updated. |
| PROFILE_ENABLED | CHAR(1) NOT NULL WITH DEFAULT 'Y' | Indicates whether the profile is enabled. This column can have one of the following values:
|
| GROUP_MEMBER | VARCHAR(24) | The name of the Db2 member in a data sharing group. The column can be blank. When the column is blank, the row applies to a Db2 subsystem that is not part of a data sharing group, or to every Db2 subsystem in a data sharing group. |
| REMARKS | VARCHAR(762) | Comments about this profile. |
| ROLE | VARCHAR(128) WITH DEFAULT NULL | The role of a monitored user or users. This value is optional if the value of AUTHID is specified. This value must be null if values are specified for LOCATION, PKGNAME, or COLLID. You can use a single-byte asterisk value ('*') in this column to specify that the profile matches all connections or threads that connect to the Db2 subsystem. However, for any thread or connection that matches multiple profiles, Db2 applies only the single most specific profile, in the following order of precedence:
When an asterisk is used, the specified limit applies separately to the number of connections or threads allowed for each requester.![]() ![]() |
| PRDID | CHAR(8) WITH DEFAULT NULL | The product-specific identifier of a monitored remote requester. The product identifier is an 8-byte alphanumeric field. The format of product identifier values is pppvvrrm, where ppp is a 3-letter product code (such as DSN for Db2), vv is the version, rr is the release, and m is the modification level. For example, DSN11015 identifies Db2 11 in new-function mode, the value is ‘DSN11015'. The product code (ppp) is one of the following values:
This value must be null if values are specified for AUTHID, PKGNAME, COLLID, or ROLE.
![]()
You can use an asterisk (*) wildcard in this column to specify that multiple values match the criteria for this profile. However, for any thread or connection that matches multiple profiles, Db2 applies only the single most specific profile, in the following order of precedence:
![]() For example, if the column value is 'DSN*', the profile applies to any Db2 for z/OS. |
| CLIENT_APPLNAME | VARCHAR(255) | The client application name information. It contains the value of the application name or transaction name from the client information that is specified for the connection. This value corresponds to the CURRENT CLIENT_APPLNAME special register.
You can use a single-byte asterisk value ('*') in this column to specify that the profile matches all connections or threads that connect to the Db2 subsystem. However, for any thread or connection that matches multiple profiles, Db2 applies only the single most specific profile, in the following order of precedence:
When an asterisk is used, the specified limit applies separately to the number of connections or threads allowed for each requester.![]() ![]() |
| CLIENT_USERID | VARCHAR(255) | The client user ID name information. It contains the value of the client user ID from the client information that is specified for the connection. This value corresponds to the CURRENT CLIENT_USERID special register.
You can use a single-byte asterisk value ('*') in this column to specify that the profile matches all connections or threads that connect to the Db2 subsystem. However, for any thread or connection that matches multiple profiles, Db2 applies only the single most specific profile, in the following order of precedence:
When an asterisk is used, the specified limit applies separately to the number of connections or threads allowed for each requester.![]() ![]() |
| CLIENT_WRKSTNNAME | VARCHAR(255) | The client workstation name information. It contains the value of the workstation name from the client information that is specified for the connection. This value corresponds to the CURRENT CLIENT_WRKSTNNAME special register.
You can use a single-byte asterisk value ('*') in this column to specify that the profile matches all connections or threads that connect to the Db2 subsystem. However, for any thread or connection that matches multiple profiles, Db2 applies only the single most specific profile, in the following order of precedence:
When an asterisk is used, the specified limit applies separately to the number of connections or threads allowed for each requester.![]() ![]() |

