IBM Books

DB2 Connect User's Guide

Listing DCS Application Status

As of DB2 Connect V5.2, the System Monitor provides three forms of the LIST DCS APPLICATIONS command, as follows:

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 an APPC connection (DB2 Connect Enterprise Edition Version 6 to DB2 Universal Database for OS/390): 

 
   Auth Id  Application Name     Appl.      Host 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 6 to DB2 Universal Database for OS/390): 

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

Auth.Id
The authorization ID that was used to log on to the host or AS/400 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. 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.

Host Application ID
One of the following:

This unique identifier is generated when the application connects to the host or AS/400 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            Seq# Client   
                              Handle                                           DB Alias 
-------- -------------------- ---------- -------------------------------- ---- -------- 
NEWTON   db2bp                0          09151251.07D3.980925183850       0001 MVSDB    
 
 Client   Client   Client     Host Application Id              Seq# Host DB Name  
 Node     Release  Codepage                                             
 -------- -------- ---------- -------------------------------- ---- -------------------- 
 antman   SQL05020 819        G9151251.G7D4.980925183851       0000 GILROY              
 
Host
Release
--------
DSN05011

This report is unformatted, and for this reason you may find the LIST DCS APPLICATIONS EXTENDED report more useful.

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 host or AS/400 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 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:

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 host or AS/400 database server databases, the host or AS/400 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 host or AS/400 database server product (for example, DSN for DB2 Universal Database for OS/390, ARI for DB2 for VSE & VM, or QSQ for DB2 Universal Database 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.

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 specifed on the command, plus nine new fields:

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                      = 09151251.0AA7.981015204853
  Sequence number                          = 0001
  Authorization ID                         = NEWTON
  Application name                         = db2bp
  Application handle                       = 1
  Application status                       = waiting for request
  Status change time                       = 10-15-1998 16:50:29.489160
  Client node                              = antman
  Client release level                     = SQL05020
  Client platform                          = AIX
  Client protocol                          = TCP/IP
  Client codepage                          = 819
  Process ID of client application         = 39324
  Client login ID                          = smith
  Host application ID                      = G9151251.GAA8.981015204854
  Sequence number                          = 0000
  Database alias at the gateway            = MVSDB
  DCS database name                        = DCSDB
  Host database name                       = GILROY
  Host release level                       = DSN05011
  Host CCSID                               = 500

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

  1. connect pending - outbound. This means that the request to connect to a host database has been issued, and DB2 Connect is waiting for the connection to be established.

  2. waiting for request. This means that the connection with the host database has been established, and that DB2 Connect is waiting for an SQL statement from the client application

  3. waiting for reply. This means that the SQL statement has been sent to the host 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.

Using the DB2 Control Center to List Extended DCS Applications Information

You can use the DB2 Version 6 Control Center to perform DB2 Connect gateway monitoring. This section shows how you can use the Control Center to display the same report as provided by the LIST DCS APPLICATIONS EXTENDED command.

To view the extended report for any application:

  1. Expand the tree under the systems icon of the Control Center to display Systems->Instances->Gateway Connections. If you right-click the mouse on any instance under the "Gateway Connections" folder, a pop-up menu will appear. Select the Applications... item from this menu. The Applications window appears. This window has a tabbed notebook appearance, with one tab titled "Applications". If there are gateway applications in your instance, there will be a second tab titled "Gateway Applications".

  2. The main window of each page contains columns of information corresponding to the fields of the LIST DCS APPLICATIONS EXTENDED report. The first six columns, visible in the window, provide the following data: 
         Client Node
     Application Name
     Client Application ID
     Host Application ID
     Database Alias at Gateway
     Status
    The rest of the fields of the report can be viewed by moving the horizontal scroll bar at the bottom of the window.

All of the fields listed by the LIST DCS APPLICATIONS EXTENDED command are present in this view.

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

[ DB2 List of Books | Search the DB2 Books ]