Db2 Connect Server - Package Statistics

This panel shows package statistics 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.


________________ ZTCNP    VTM     O2       V550./C DA61 03/06/14 13:03:23   2  
> Help PF1                                                            Back PF3  
>                                                                               
>       THREAD INFORMATION:  Enter a selection letter on the top line.          
>                                                                               
> A-DB2 Connect Server  B-Overview   C-Statement Info   *-Package Statistics    
>                                                                               
=============================================================================== 
>                DB2 Connect Server - Package Statistics                        
 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                                          
 tcnp                                                                           
+                                                                               
+                  Send   Received   Send Top   Rec'd Top  Send Bot   Rec'd Bot 
+ Outbound     --------   --------   --------   ---------  --------   --------- 
+ Data             1014        873        524         463       490         410 
+                                                                               
+                                                                               
+                   128        256       512        1024       2048       4096  
+ Outbound     --------   --------   --------   --------   --------   --------  
+ Send Data           0          0          1          1          0          0  
+ Rec'd Data          0          0          2          0          0          0  
+                                                                               
+                                                                               
+                  8192      16384      31999      64000      GT64K             
+ Outbound     --------   --------   --------   --------   --------             
+ Send Data           0          0          0          0          0             
+ Rec'd Data          0          0          0          0          0             
+                                                                               
+                                                                               
+                  2 ms       4 ms       8 ms      16 ms      32 ms    GT32 ms  
+ Network      --------   --------   --------   --------   --------   --------  
+ Time              N/P          0        N/P          0        N/P        N/P  
===============================================================================

Navigation

For additional information about

related topics, select one of the options at the top of the panel.
other topics, use the PF keys.

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.; Attach information is displayed only if the thread is a distributed allied thread (not for distributed database access threads).

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.

Package: The Db2 package name of the active thread. Up to 18 characters of the package name are returned.
Collection: The package collection identifier. This field is displayed only if a package is being used.

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=token

The 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/A is shown, the Db2C Master is currently being changed.

Outbound data fields:

Outbound Data 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 Data 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.

Outbound Data Sent Top

Shows the maximum number of bytes sent by the Db2 Connect gateway to the host.

On statement level, this is the maximum value on a per statement base measured during the processing of all statements against the Database Connection Services (DCS) database.

On data transmission level, this is the maximum value occurring in the DCS application during the processing of all statements that used the displayed number of data transmissions.

Outbound Data Received Top

Shows the maximum number of bytes received per statement by the Db2 Connect gateway from the host during the processing of all statements against this DCS database, or in this DCS application, that used this number of data transmissions.

Outbound Data Sent Bottom

Shows the lowest number of bytes sent per statement by the Db2 Connect gateway to the host during the processing of all statements against this DCS database, or in this DCS application, that used this number of data transmissions.

Outbound Data Received Bottom

Shows the lowest number of bytes received per statement by the Db2 Connect gateway from the host during the processing of all statements against this DCS database, or in this DCS application, that used this number of data transmissions.

Outbound data sent/received fields:

Statement Transaction: max data sent/received 128: Shows the number of statements with outbound bytes sent/received from 1 through 128.
Statement Transaction: max data sent/received 256: Shows the number of statements with outbound bytes sent/received from 129 through 256.
Statement Transaction: max data sent/received 512: Shows the number of statements with outbound bytes sent/received from 257 through 512.
Statement Transaction: max data sent/received 1024: Shows the number of statements with outbound bytes sent/received from 513 through 1024.
Statement Transaction: max data sent/received 2048: Shows the number of statements with outbound bytes sent/received from 1025 through 2048.
Statement Transaction: max data sent/received 4096: Shows the number of statements with outbound bytes sent/received from 2049 through 4096.
Statement Transaction: max data sent/received 8192: Shows the number of statements with outbound bytes sent/received from 4097 through 8192.
Statement Transaction: max data sent/received 16384: Shows the number of statements with outbound bytes sent/received from 8193 through 16384.
Statement Transaction: max data sent/received 31999: Shows the number of statements with outbound bytes sent/received from 16385 through 31999.
Statement Transaction: max data sent/received 64000: Shows the number of statements with outbound bytes sent/received from 32000 through 64000.
Statement Transaction: max data sent/received GT64K: Shows the number of statements with outbound bytes sent/received greater than 64000.

Network time fields:

Statement Transaction: max time 2ms: Shows the number of statements whose network time was less then, or equal to, 2 milliseconds.
Statement Transaction: max time 4ms: Shows the number of statements whose network time was greater than 2 milliseconds but less than, or equal to, 4 milliseconds.
Statement Transaction: max time 8ms: Shows the number of statements whose network time was greater than 4 milliseconds but less than, or equal to, 8 milliseconds.
Statement Transaction: max time 16ms: Shows the number of statements whose network time was greater than 8 milliseconds but less than, or equal to, 16 milliseconds.
Statement Transaction: max time 32ms: Shows the number of statements whose network time was greater than 16 milliseconds but less than, or equal to, 32 milliseconds.
Statement Transaction: max time GT32ms: Shows the number of statements whose network time was greater than 32 milliseconds.