DB2 Connect Version 10.1 for Linux, UNIX, and Windows

DCS application status

Use the Database Connection Services (DCS) application status to retrieve information about the applications connected to the database. There are three application status commands you can use, which return different levels of detail.

The System Monitor provides three forms of the LIST DCS APPLICATIONS command, as follows:

LIST DCS APPLICATIONS
LIST DCS APPLICATIONS SHOW DETAIL
LIST DCS APPLICATIONS EXTENDED

In the output that follows, the format for the Host Application ID and Client Application ID can differ depending on the IBM mainframe database version and the TCP/IP support level.

Table 1. Application ID format based on host version and TCP/IP support level
Scenario	Application ID format
Clients accessing data servers with RDB Manager Level support less than 7	`G91A0D3A.P8BC.060306212019`
Clients accessing data servers with RDB Manager level support 8 or greater over TCP/IP v4	`9.26.13.61.65289.060306213816`
Clients accessing data servers with RDB Manager level support 8 or greater over TCP/IP v6	`2002:91a:519:13:209:6bff:fe14:4fbb.7684.060306213741`

LIST DCS APPLICATIONS

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 a TCP/IP connection (DB2 Connect™ to DB2® for z/OS®):

Auth Id Application Name Appl.  Host Application Id
                         Handle
------- ---------------- ------ ----------------------------------------------------
NEWTON  db2cli.exe       7      G91A0D3A.P8BC.060306212019
NEWTON  db2cli.exe       25     9.26.13.61.65289.060306213816
NEWTON  db2cli.exe       20     2002:91a:519:13:209:6bff:fe14:4fbb.7684.060306213741

Auth.Id

The authorization ID that was used to log on to the IBM mainframe database 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.

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. The agent ID is also required when using the FORCE USERS command or API.

Host Application ID

One of the following items:

The DRDA® correlation token (CRRTKN), for unprotected conversations.
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 IBM mainframe database server. You can use this element in conjunction with the Application ID to correlate the client and server parts of the application information.

LIST DCS APPLICATIONS SHOW DETAIL

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

Auth Id                        Application Name     Appl.      Client Application Id                          
                                                    Handle                                                         
------------------------------ -------------------- ---------- ----------------------------------------------------
NEWTON                         db2cli.exe           37         2002:91a:519:13:209:6bff:fe14:4fbb.8196.060306214224


Seq#  Client   Client   Client   Client     Host Application Id       
      DB Alias Node     Release  Codepage                             
----- -------- -------- -------- ---------- --------------------------
00001 MDB      SAYYID   SQL09000 1252       G91A0D3A.P982.060306214231


Seq#  Host DB Name         Host    
                           Release 
----- -------------------- --------
00001 MEXICO               DSN08015

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.

This value lets you correlate connections from clients to the DB2 Connect workstation and from the DB2 Connect workstation to the IBM mainframe database 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 running. The information varies according to the client protocol in use. For a client connected through TCP/IP, the host name is displayed. For Java applications that use the IBM Data Server Driver versions 3.65, 4.15 or later, the IP address is displayed rather than host name if db2.jcc.enableInetAddressGetHostName is set to false.

Client Product ID (Client)

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

SQL07010 for Version 7.1 of DB2 Universal Database™ and DB2 Connect products and their clients.
SQL08010 for Version 8.1 of DB2 Universal Database and DB2 Connect products and their clients.
SQL08020 for Version 8.2 of DB2 Universal Database and DB2 Connect products and their clients.
SQL09120 for Version 9.1 of DB2 products, 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 IBM mainframe database server databases, the IBM mainframe database 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 IBM mainframe database server product (for example, DSN for DB2 Universal Database for z/OS and OS/390®, ARI for DB2 Server for VSE & VM, or QSQ for IBM® DB2 for IBM i)
VV: Represents a two-digit version number, such as 08.
RR: Represents a two-digit release number, such as 01.
M: Represents a one-character modification level (0-9 or A-Z).

LIST DCS APPLICATIONS EXTENDED

You can use the LIST DCS APPLICATIONS command with the option EXTENDED in order to generate an Extended Report. The Extended Report lists all the fields that are listed when the SHOW DETAIL option is specified on the command, plus nine new fields:

DCS application status
Status change time
Client platform
Client protocol
Host Coded Character Set Identifier (CCSID).
Client login ID
Process ID of client application
Database alias at the gateway
DCS database name

While the existing command options list the fields horizontally, one line per application, the new option lists them vertically, one field per line.

Here is the new syntax of the command:

   LIST DCS APPLICATIONS [ SHOW DETAIL | EXTENDED ]

And here is sample output from this command, when using the new option EXTENDED:

               List of DCS Applications - Extended Report
      
Client application ID       = 2002:91a:519:13:209:6bff:fe14:4fbb.8196.060306214224
Sequence number                  = 00001
Authorization ID                 = NEWTON
Trusted Authorization ID         =
Application name                 = db2cli.exe
Application handle               = 37
Application status               = waiting for request
Status change time               = Not Collected
Client node                      = SAYYID
Client release level             = SQL09000
Client platform                  = NT
Client protocol                  = TCP/IP
Client codepage                  = 1252
Process ID of client application = 1192
Client login ID                  = ISAYYID
Host application ID              = G91A0D3A.P982.060306214231
Sequence number                  = 00001
Database alias at the gateway    = MDB
DCS database name                = MDB
Host database name               = MEXICO
Host release level               = DSN08015
Host CCSID                       = 1208

The application status field contains one of the following three values:

connect pending - outbound. This means that the request to connect to a IBM mainframe database has been issued, and DB2 Connect is waiting for the connection to be established.
waiting for request. This means that the connection with the IBM mainframe database has been established, and that DB2 Connect is waiting for an SQL statement from the client application
waiting for reply. This means that the SQL statement has been sent to the IBM mainframe database.

Also, the status change time is only shown in the report if the System Monitor UOW switch was turned on during processing. Otherwise, "Not Collected" will be shown.