Snapshot Level Application Lock DCS Application |
Logical Data Grouping appl_id_info appl_lock dcs_appl_info |
Monitor Switch Basic Basic Basic |
Resettable |
No |
|
Event Type Connection Statement |
Logical Data Grouping connheader_event stmt_event subsection_event |
|
Element Name Element Type |
agent_id information |
Description: A system-wide unique ID for the application. On multi-node systems, where a database is partitioned, this ID will be the same on every node where the application may make a secondary connection.
Usage: The application handle can be used to uniquely identify an active application (application handle is synonymous with agent Id).
Note: | The Application Handle (agent ID) data element has different behavior depending on your version of DB2. When taking snapshots from DB2 Version 1 or Version 2 to a DB2 Universal Database (Version 5 or greater) database, the agent_id returned is not usable as an application identifier. In these cases an agent_id is still returned for back-level compitability, but internally the DB2 Universal Database server will not recognize the value as an agent_id. |
It can be used as input to GET SNAPSHOT commands that require an agent Id.
When reading event traces, it can be used to match event records with a given application.
It can be used as input to the FORCE APPLICATION command or API. On multi-node systems this command can be issued from any node where the application has a connection. Its effect is global