SQL Call Being Executed

This panel shows the current SQL statement that a DB2 thread is executing. OMEGAMON® XE for DB2 PE automatically determines whether the SQL statement is dynamic or static and displays appropriate text to that effect.


________________ ZSQL     VTM     O2       V540.#P DA41 11/04/13  9:14:13   2  
> Help PF1                                                            Back PF3  
                                                                                
>       THREAD INFORMATION:  Enter a selection letter on the top line.          
                                                                                
> A-THREAD DETAIL B-LOCK COUNTS C-LOCK WAITS     D-LOCKS OWNED  E-GLOBAL LOCKS  
> *-CURRENT SQL   G-SQL COUNTS  H-DISTRIBUTED    I-BUFFER POOL  J-GROUP BP      
> K-PACKAGES      L-RES LIMIT   M-PARALLEL TASKS N-UTILITY      O-OBJECTS       
> P-CANCEL THREAD Q-DB2 CONSOLE R-DSN ACTIVITY   S-APPL TRACE   T-ENCLAVE       
> U-LONG NAMES    V-SQL PA      W-ACCEL ACTIVITY                                
=============================================================================== 
>                           SQL CALL BEING EXECUTED                             
 PLAN                                                                           
+ Thread:  Plan=DSNESPRR  Connid=TSO      Corrid=MIS          Authid=MIS        
+ Attach:  TSO            Userid=MIS                          Region asid= 224  
+ Package: DSNESM68                       Collection=DSNESPRR                   
+ Luwid=DEIBMIPS.IPSATA41.CC365C8D3696=806                                      
 call                                                                           
+      SQL call is active, call information is as follows :                     
+                                                                               
+      Thread Status  = NOT-IN-DB2     SQL Request Type     = DYNAMIC           
+      Total SQL Reqs =    28634       SQL Call Type        = EXECUTE           
+      SQL DBRM Name  = DSNESM68       SQL Statement Number = 00277             
+      Collection ID  = DSNESPRR                                                
+                                                                               
+      INSERT INTO MIS.TESTTAB01                                                
+             (IFCID,NAME,DESCRIPTION,SEQ)                                      
+             VALUES(ROUND(RAND()*25000,0),'Name','Desc',0)                     
===============================================================================

Navigation

For additional information about

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

Fields

Thread identifier: OMEGAMON XE for DB2 PE 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.
Authid: The Db2 authorization identifier of the active thread.

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.

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.

Distributed thread identifier: The following fields are displayed when 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.

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 such as the following:


USCACO01.O2D22A.A1FE8E04B9D4=8

SQL call information: The information that OMEGAMON XE for DB2 PE displays in this area varies slightly, depending on whether the SQL call is active or not. If the call is active, OMEGAMON XE for Db2 PE displays the information described below with the actual text of the SQL call. If the call is not active, OMEGAMON XE for Db2 PE displays only the information described below.

Thread Status: The current Db2 status of the thread.
SQL Request Type: The type of the SQL request: dynamic SQL or static SQL.
Total SQL Reqs: The total number of SQL requests issued by the thread.
SQL Call Type: The SQL call type of the currently or previously active SQL call. This is the specific activity that DB2 is performing. For example, a dynamic SQL call can indicate PREPARE, EXECUTE, or OPEN CURSOR even though the original SQL statement might have been an SQL SELECT. A static SQL call can indicate OPEN CURSOR, CLOSE CURSOR, or FETCH even though the originating SQL statement was an SQL DECLARE CURSOR.
SQL DBRM Name: The database request module name containing the active call. The DBRM name is usually set to the application program name. It helps you to locate the program that is issuing the call if diagnosis is necessary.
SQL Statement Number: The Db2 precompiler statement number of the active SQL statement. The statement number, when used together with the DBRM name, helps you easily locate the specific SQL call for diagnostic purposes.
Collection ID: The Collection ID of the currently executing statement. This field is displayed only if the currently executing statement is contained in a package.