Db2 Connect Server - Overview
This panel shows application-, client-, and Db2 host-related information for the previously selected Distributed Database Access Thread (DBAT).
If the distributed thread does not have a connection through a Db2 Connect gateway, or if the Performance Expert Agent for Db2 Connect Monitoring (PE Agent) is not installed or not
running on the Db2 Connect Server, the message
No Db2 Connect server data available is displayed.
________________ ZTCNO VTM O2 V540./C DA61 03/06/14 12:54:54 2
> Help PF1 Back PF3
>
> THREAD INFORMATION: Enter a selection letter on the top line.
>
> A-DB2 Connect Server *-Overview C-Statement Info D-Package Statistics
>
==============================================================================
> DB2 Connect Server - Overview
PLAN
+ Thread: Plan=DISTSERV Connid=SERVER Corrid=javaw Authid=MIS
+ Dist : Type=DATABASE ACCESS, Luwid=G9987A90.A2F1.CCCFEFB7D0DA=214
+ Location : ::FFFF:9.152.122.144
+ Host Name:polk.boeblingen.de.ibm.com
tcno
+
+ Application Information
+ -----------------------------------------------------------------
+ Application Handle (agent ID) = 57794
+ Application Name = javaw
+ Application ID = *LOCAL.db2inst1.140311064128
+ Transaction ID = N/P
+ Authorization ID = MIS
+
+ Code Page Used by Application = 1208
+ Client Process ID = 23948
+ Client Operation Platform = LINUXX8664
+ Client Communication Protocol = LOCAL
+ Host Coded Character Set ID = 1208
+ Configuration Name of Client = polk
+ Client Product/Version ID = SQL09078
+ Inbound Communication Address = *LOCAL.db2inst1
+
+ DCS Application Status = UOWWAITOUTBOUND
+ Application Status Change Time = 2014-03-06-12.46.52.280000
+ User Logon ID = root
+ Sequence Number = 00001
+ Database Alias at Gateway = OMP6DA61
+ DCS Database Name = OMP6DA61
+ Outbound Application ID = *LOCAL.db2inst1.140311064128
+ Outbound Sequence Number = 0000
+ Outbound Communication Address = 9.152.87.106 16681
+ Outbound Communication Protocol = TCPIP
+
+ Last Reset Timestamp = N/P
+ Application Idle Time = 00:00:00.000402
+
+ SQL Stmt = 3 Failed Stmt = 0
+ Failed Stmt % = .0% Open Cursor = 0
+ Commit = 0 Rollback = 0
+ Row = 0 Transmissions = 2
+
+ Client
+ --------------------------------------------------------------
+ DB2 Connect First Connection = 2014-03-06-12.46.52.130000
+ Unit of Work Start Timestamp = 2014-03-06-12.46.52.237000
+ Unit of Work Stop Timestamp = N/P
+ Previous UOW Completion Timestamp = N/P
+ Unit of Work Completion Status = N/P
+ Elapsed Time DB2CONN Execution = 00:00:00.000118
+ Most Recent UOW Elapsed Time = 00:00:00.000000
+
+ DB2 Host
+ --------------------------------------------------------------------------
+ Database Name = OMPDA61 Inbound Byte Sent = 327
+ Product/Version ID = DSN10015 Inbound Byte Received = 982
+ Response Time = 00:00:00.036974 Outbound Byte Sent = 1014
+ Stmt Exec Elapsed Time= 00:00:00.036118 Outbound Byte Received = 410
===============================================================================Fields
Thread identifier: This information identifies the thread to which the information in this
panel applies.
- Plan
- The Db2 plan name of the active thread.
- Connid
- The Db2 connection identifier of the active thread.
- Corrid
- The Db2 correlation identifier of the active thread. If the correlation is not set, N/A is displayed.
- Authid
- The Db2 authorization identifier of the active thread.
- Attach
- Depending on the type of connection, the appropriate information is displayed.
- Connection Type
-
- Batch
- The MVS jobname and ASID.Note: For threads from remote Db2, the MVS job name is N/A.
- CICS®
- The CICS jobname, task name, task number, terminal ID,
and thread type. The thread type is:
- Pool
- The thread in use is a pool thread.
- Entry
- The thread in use is a nonprotected entry thread.
- Prot
- The thread in use is a protected thread. Protected threads are defined in an RCT entry definition using the THRDS operand.
- IMS
- The IMS region number, transaction name, region name, and terminal ID (LTERM).
- RRSAF
- The MVS job name and ASID.Note: For threads from remote Db2, the MVS job name is N/A.
- System
- The originating Db2 job name and the resource manager that is the source of the thread. An additional line below the Attach line identifies the user thread, if any, being served by the system thread.
- TSO
- The TSO user ID and region ASID.
- Utility
- No additional information.
- Db2
- The Db2 subsystem identifier.
- MVS
- The MVS system identifier.
- ORIGAUTH
- The original (primary) Db2 authorization identifier of the thread. This field displays only when the original identifier is different from the Authid.
Package identifier: This information identifies the package to which the information in
this panel applies.
Distributed thread identifier: The following fields are displayed if the thread has a
distributed relationship with a remote Db2 subsystem.
- Type
- The distributed thread type.
- Distributed Allied
- A requesting thread; one that has issued an SQL call to a remote Db2 location.
- Database Access
- A responding thread; one that is serving a remote Db2 location by responding to an SQL call.
- Db2=
- The Db2 subsystem ID, indicating the member of the data sharing group of this thread.
- Luwid
- This value consists of two parts: the logical unit of work ID (luw-id) and a
token. The token can be used in place of the luw-id in any Db2
command that accepts luw-id as input. Format:
luw-id=tokenThe luw-id consists of the network name, the originating VTAM® LUNAME, and a unique identifier (separated by periods). Thus, the Luwid field displays data like in the following example:
USCACO01.O2D22A.A1FE8E04B9D4=8 - System
- The originating Db2 job name and the resource manager that is the source of the thread. An additional line below the Attach line identifies the user thread, if any, being served by the system thread.
- DB2C Master
- Shows the name of the member of the data sharing group that controls Db2 Connect monitoring for the group. If
N/Ais shown, the DB2C Master is currently being changed. For more information, see the description of panel Redirect Monitoring to Another Db2.
Application information:
- Application Handle (agent ID)
- Shows the system-wide unique ID for the application.
- Application Name
- Shows the name of the application running at the client as known to the Db2 Connect.
- Application ID
- Shows the identifier that is generated when the application connects to the database manager or when Distributed Database Connection Server (DDCS) receives a request to connect to a DRDA database.
- Transaction ID
- Shows the unique transaction identifier across all databases generated by a transaction manager in a two-phase-commit transaction.
- Authorization ID
- Shows the authorization ID of the user who invoked the application.
- Code Page Used by Application
- Shows the code page identifier.
- Client Process ID
- Shows the process ID of the client application that made the connection to the database.
- Client Operation Platform
- Shows the operating system on which the client application is running.
- Client Communication Protocol
- Shows the communication protocol that the client application is using to communicate with the server.
- Host Coded Character Set ID
- Shows the coded character set identifier (CCSID) of the host database.
- Configuration Name of Client
- Shows the NNAME in the database manager configuration file at the client node.
- Client Product/Version ID
- Shows the communication address of the client. It could be an SNA net ID and LU partner name, or an IP address and port number for TCP/IP.
- Inbound Communication Address
- Shows the product and version that is running on the client.
- DCS Application Status
- Shows the current status of the application.
- Application Status Change Time
- Shows the date and time the application entered its current status.
- User Login ID
- Shows the ID that the user specified when logging in to the operating system.
- Sequence Number
- Increments whenever a unit of work ends, that is, when a COMMIT or ROLLBACK terminates a unit of work.
- Database Alias at Gateway
- Shows the alias used at the Db2 Connect gateway to connect to the host database.
- DCS Database Name
- Shows the name of the remote database as cataloged in the DCS directory.
- Outbound Application ID
- Is generated when the application connects the DRDA host database.
- Outbound Sequence Number
- Is generated when the application connects the DRDA host database.
- Outbound Communication Address
- Shows the communication address of the target database.
- Outbound Communication Protocol
- Shows the communication protocol used between the Db2 Connect gateway and host.
- Last Reset Timestamp
- Shows the date and time that the monitor counters were reset for the application issuing the GET SNAPSHOT.
- Application Idle Time
- Shows the number of seconds since an application issued any requests to the server.
- SQL Stmt
- Shows the number of SQL statements that have been attempted since the latter of: application startup, database activation, or last reset.
- Failed Stmt
- Shows the number of SQL statements that were attempted, but failed.
- Failed Stmt %
- Shows the percentage of failed statements versus all SQL statements.
- Open Cursor
- Shows the number of cursors currently open for an application.
- Commit
- Shows the total number of SQL COMMIT statements that have been attempted.
- Rollback
- Shows the total number of SQL ROLLBACK statements that have been attempted.
- Row
- Shows the number of rows that have been selected and returned to the application.
- Transmissions
- Shows the number of data transmissions between Db2 Connect gateway and host that was used to process this DCS statement. (One data transmission consists of one send or one receive).
Client fields:
- Db2 Connect First Connection
- Shows the date and time at which the first connection to the host database was initiated from the Db2 Connect gateway.
- Unit of Work Start Timestamp
- Shows the date and time at which the unit of work first required database resources.
- Unit of Work Stop Timestamp
- Shows the date and time at which the most recent unit of work completed which occurs when database changes are committed or rolled back.
- Previous UOW Completion Timestamp
- Shows the time the unit of work completed.
- Unit of Work Completion Status
- Shows the status of the unit of work and how it stopped. It can
have:
- Committed because of a COMMIT statement
- Rolled back because of a ROLLBACK statement
- Rolled back because of a deadlock
- Rolled back due to an abnormal termination
- Committed at normal application termination
- Unknown as a result of a FLUSH EVENT MONITOR command for which units of work were in progress.
- Elapsed Time Db2CONN Execution
- Shows the time, in seconds and microseconds, at the Db2 Connect gateway to process an application request (since the connection was established), or to process a single statement.
- Most Recent UOW Elapsed Time
- Shows the elapsed execution time of the most recently completed unit of work.
Db2 Host fields:
- Database Name
- Shows the real name of the host database for which information is being collected or to which the application is connected. This is the name that was given to the database when it is created.
- Product/Version ID
- Shows the product and version that is running on the Db2 data server in the form pppvvrrm, where:
- ppp stands for SQL
- vv identifies a 2-digit version number (with high-order 0 in the case of a 1-digit version)
- rr identifies a 2-digit release number (with high-order 0 in the case of a 1-digit release)
- m identifies a 1-digit modification level
- Response Time
- For a DCS statement, this is the elapsed time between the time that the statement was sent from the Db2 Connect gateway to the host for processing and the time when the result was received from the host.
- Stmt Execution Elapsed Time
- For a DCS statement, this is the elapsed time spent processing an SQL request on a host database server.
- Inbound Byte Sent
- Shows the number of bytes sent by the Db2 Connect gateway to the client, excluding communication protocol overhead (for example, TCP/IP or SNA headers).
- Inbound Byte Received
- Shows the number of bytes received by the Db2 Connect gateway from the client, excluding communication protocol overhead (for example, TCP/IP or SNA headers).
- Outbound Byte Sent
- Shows the number of bytes sent by the Db2 Connect gateway to the host excluding communication protocol overhead (for example, TCP/IP or SNA headers).
- Outbound Byte Received
- Shows the number of bytes received by the Db2 Connect gateway from the host, excluding communication protocol overhead (for example, TCP/IP or SNA headers).