Monitoring connections for remote clients

You can use the database system monitor with a Db2 Connect Server product, such as Db2 Connect Enterprise Edition, to monitor the remote client connections.

To monitor clients that are local to the Db2 Connect Server server, that are running on the server itself, you will need to set the following variable: 
   db2set DB2CONNECT_IN_APP_PROCESS=NO
For example, when an error occurs at the IBM mainframe system, the system administrator can determine if the problem was on the Db2 Connect workstation. The database system monitor correlates:
  • The DRDA correlation token (CRRTKN), for unprotected conversations.
  • The unit of work id (UOWID), for two-phase connections protected by the DRDA-3 sync point manager (as used over TCP/IP connections).
  • The Db2 Connect connection identifier (the Application ID).
This information shows which Db2 Connect connection caused the problem, which allows the system administrator to force the individual client application from the system without affecting the other clients using the Db2 Connect connection.

Listing the Status of Monitor Switches

To list the status of monitor switches, use the db2 get monitor switches command.