The name of the application running at the client, as known to the database or DB2 Connect™ server.
Table Function | Monitor Element Collection Level |
---|---|
MON_GET_CONNECTION table function - Get connection metrics | Always collected |
MON_GET_CONNECTION_DETAILS table function - Get detailed connection metrics (reported in DETAILS XML document) | Always collected |
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Application | appl_id_info | Basic |
Lock | appl_lock_list | Basic |
DCS Application | dcs_appl_info | Basic |
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Locking | - | - |
Unit of work | - | - |
Connections | event_connheader | - |
Activities | event_activity | - |
Threshold violations | event_thresholdviolations | - |
This element can be used with appl_id to relate data items with your application.
In a client-server environment, this name is passed from the client to the server when establishing the database connection. Any non-English characters in the application name will be removed. A CLI application can set the SQL_ATTR_INFO_PROGRAMNAME attribute with a call to SQLSetConnectAttr. When SQL_ATTR_INFO_PROGRAMNAME is set before the connection to the server is established, the value specified overrides the actual client application name and will be the value that is displayed in the appl_name monitor element.
In situations where the client application code page is different from the code page under which the database system monitor is running, you can use codepage_id to help translate appl_name.