Applications -- Fields and controls

Local Databases page
Gateway page
" " Force
" " Force All
" " Refresh
" " Close



Local Databases page

The Local Databases page displays the following local application information:

" " Connection
" " Database Name
" " Application Name
" " Status
" " Client login ID
" " Application Handle
" " Authorization ID
" " Status Change Time

" " Connection

The identifier generated when the application connects to the database at the database manager.

" " Database Name

The real name of the database to which the application is connected. This is the name that the database was given when it was created.

" " Application Name

The name of the application running on the client that identifies it to the database manager or DB2 Connect.

" " Status

The current status of the application.

" " Client Login ID

The ID that the user specified when logging in to the operating system. This ID is distinct from the Authorization ID, which the user specifies when connecting to the database.

" " Application Handle (agent ID)

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.

" " Authorization ID

The authorization ID of the user who invoked the application. On a gateway node this is the user's authorization ID on the host.

" " Status Change Time

The date and time the application entered its current status.



Gateway page

The Gateway page displays the following DB2 Connect application information:

" " Client Application ID
" " Client Node
" " Application Name
" " Host Application ID (LUWID)
" " Database Alias at Gateway
" " Status
" " Status Change Time
" " Client Login ID
" " Client Platform
" " Client Protocol
" " Client Address
" " DCS Database Name
" " Host Database Name
" " Host Protocol
" " Host Address
" " Application Handle
" " Authorization ID

" " Client Application ID

The identifier generated when the application connects to the database at the database manager, or when DB2 Connect receives a request to connect to a DRDA database.

" " Client Node

The nname in the database manager configuration file at the client node.

" " Application Name

The name of the application running on the client that identifies it to the database manager or DB2 Connect.

" " Host Application ID (LUWID)

The identifier generated when an application connects to a DRDA database. It is used to connect the DB2 Connect gateway to the host.

" " Database Alias at Gateway

The alias used at the DB2 Connect gateway to connect to the host database.

" " Status

The status of a gateway application at the DB2 Connect gateway.

" " Status Change Time

The date and time the application entered its current status.

" " Client Login ID

The ID that the user specified when logging in to the operating system. This ID is distinct from the Authorization ID, which the user specifies when connecting to the database.

" " Client Platform

The operating system on which the client application is running.

" " Client Protocol

The communication protocol that the client application is using to communicate with the server.

" " Client Address

The communication address of the client. For example, it could be an SNA net ID and LU partner name, or an IP address and a port number for TCP/IP.

" " DCS Database Name

The name of the DCS database as catalogued in the DCS directory.

" " Host Database Name

The real name of the host database to which the application is connected. This is the name that was given to the database when it was created.

" " Host Protocol

The communication protocol used between the DB2 Connect gateway and the host.

" " Host Address

The communication address of the target database. For example, it could be an SNA net ID and LU partner name, or an IP address and a port number for TCP/IP.

" " Application Handle (agent ID)

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.

" " Authorization ID

The authorization ID of the user who invoked the application. On a gateway node this is the user's authorization ID on the host.



" " Force

Click on this push button to forcibly disconnect one or more applications from a database.

" " Force All

Click on this push button to forcibly disconnect all applications from all databases for an instance.

" " Refresh

Click on this push button to update the information being displayed.