User's Guide

Database System Monitor

You can use the Database System Monitor to monitor the connections for remote clients.

When an error occurs at the DRDA server, 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 logical unit of work identifier (LUWID), for two-phase conversations protected by an SNA Syncpoint Manager (SPM).
The unit of work id (UOWID), for two-phase connections protected by the DRDA-3 Syncpoint Manager (as used over TCP/IP connections).
The DB2 Connect connection identifier (the Application ID).

This 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.

For detailed information about the database system monitor and how it works, see the System Monitor Guide and Reference.

To activate the monitor, use the DB2 UPDATE MONITOR SWITCHES command. Refer to Command Reference for the syntax of this command. Here is an example, which creates DB2 System Monitor events for Units of Work (UOW):

   db2 update monitor switches using uow on

To list the status of monitor switches, use the DB2 GET MONITOR SWITCHES command.

To view the information provided by the monitor at the application level, issue the DB2 LIST DCS APPLICATIONS command. It returns the following information for an APPC connection (DB2 Connect Enterprise Edition Version 5.0 to DB2 for OS/390):

 
   Auth Id  Application Name     Appl.      Outbound Application Id
                              Handle
   -------- -------------------- ---------- --------------------------------
   USERID   db2bp_41             0          CAIBMOML.OMXT4H0A.A79EAA3C6E29

It returns the following information for a TCP/IP connection (DB2 Connect Enterprise Edition Version 5.0 to DB2 for OS/390):

 
   Auth Id  Application Name     Appl.      Outbound Application Id
                                 Handle
   -------- -------------------- ---------- --------------------------------
   USERID   db2bp_41             2          0915155C.9704.1517172201BE

Auth.Id

The authorization ID that was used to log on to the DRDA server. This identifies who is running the application.

Application Name

The name of the application running at the client as known to DB2 Connect. Only the first 20 bytes after the last path separator are available. The application name is not available for applications running on DB2 for OS/2 Version 1.

Appl. Handle

The agent that is executing on the DB2 Connect workstation. You can use this element to link the database system monitor information to other diagnostic information. (For example, see "Trace Utility (ddcstrc)".) The agent ID is also required when using the FORCE USERS command or API.

Outbound Application ID

One of the following:

The DRDA correlation token (CRRTKN), for unprotected conversations.
The logical unit of work identifier (LUWID), for two-phase conversations protected by an SNA Syncpoint Manager (SPM).
The unit of work id (UOWID), for two-phase connections protected by the DRDA-3 Syncpoint Manager (as used over TCP/IP connections).

This unique identifier is generated when the application connects to the DRDA server database. You can use this element in conjunction with the Application ID to correlate the client and server parts of the application information.

If the DB2 LIST DCS APPLICATIONS SHOW DETAIL command format is specified, additional information is shown, including, for an APPC connection:

 
   Auth Id  Application Name     Appl.      Client Application Id
                                 Handle
   -------- -------------------- ---------- --------------------------------
   USERID   db2bp_41             0          09150FDB.9704.1517161810D5
 
   Seq# DB Alias Node     Client   Codepage   Outbound Application Id
   ---- -------- -------- -------- ---------- --------------------------------
   0001 DB2SF    weasel   SQL05000 850        CAIBMOML.OMXT4H0A.A79EAA3C6E29
 
   Seq# DB Name              Host
   ---- -------------------- --------
   0000 SAN_FRANCISCO        DSN05010

Or, for a TCP/IP connection:

   Auth Id  Application Name     Appl.      Client Application Id
                                 Handle
   -------- -------------------- ---------- --------------------------------
   USERID   db2bp_41             2          09150FDB.9704.1517172110D6
 
   Seq# DB Alias Node     Client   Codepage   Outbound Application Id
   ---- -------- -------- -------- ---------- --------------------------------
   0001 DB2SFT   weasel   SQL05000 850        0915155C.9704.1517172201BE
 
   Seq# DB Name              Host
   ---- -------------------- --------
   0000 SAN_FRANCISCO        DSN05010

Client Application ID

Uniquely identifies the application connected to the DB2 Connect workstation. There are different formats for the application ID, which are dependent on the communication protocol between the client and the DB2 Connect workstation. For more information on the formats, see the Administration Guide.

This value lets you correlate connections from clients to the DB2 Connect workstation and from the DB2 Connect workstation to the DRDA server.

Client Sequence no (Seq#)

The client sequence number is the transaction sequence number. It is used to help correlate a transaction spread over different systems.

Client DB alias

The alias of the database provided by the application to connect to the database. This element can be used to identify the actual database that the application is accessing. The mapping between this name and the database name could be done by using the database directories at the client node and the database manager server node.

Client NNAME (Node)

Identifies the node where the client application is executing. The information varies according to the client protocol in use. For example, for a client connected via NetBIOS, this is the value of the NNAME database manager configuration parameter. For a client connected via TCP/IP, this is the host name.

Client Product ID (Client)

The product and version that is running on the client. The client product IDs will be:

SQL01010 for Version 1 of DB2 for OS/2
SQL01011 for Version 1 of UNIX-based DB2 products and Client Application Enablers.
SQL02010 for Version 2 of DB2 products and Client Application Enablers.
SQL02020 for Version 2.1.2 of DB2 products and Client Application Enablers.
SQL05000 for Version 5.0 of DB2 Universal Database and DB2 Connect products and their clients.

Code Page ID

The code page identifier at the node where the monitored application started.

You can use this information to ensure that data conversion is supported between the application code page and the database code page (or for DRDA server databases, the DRDA server CCSID).

If the application code page is different from that under which the database system monitor is running, this code page element can help you to manually convert data that was passed from the application and displayed by the database system monitor. For example, you can use it to help translate the Application Name.

Outbound Sequence No

This represents the outbound sequence number. It is used for correlating transactions on different systems.

Host Database Name

The real name of the database to which the application is connected. In the DCS directory, this is the target database name.

Host Product ID

The product and version that is running on the server. It is in the form PPPVVRRM, where:

PPP: Identifies the DRDA server product (for example, DSN for DB2 for OS/390, ARI for DB2 for VSE & VM, or QSQ for DB2 for AS/400)
VV: Is a two-digit version number, such as 01
RR: Is a two-digit release number, such as 01
M: Is a one-digit modification level.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]