DISPLAY STATISTICS output

The output of a DSNC DISPLAY STATISTICS command is shown below.

Figure 1. Sample output from DSNC DISPLAY STATISTICS command

 
DFHDB2014 07/09/98 14:35:45 IYK4Z2G1 Statistics report follows for RCTJT
accessing DB2 DB3A
                                                           -----COMMITS----
DB2ENTRY PLAN        CALLS    AUTHS    W/P HIGH   ABORTS   1-PHASE  2-PHASE
*COMMAND                1        1      1    1       0          0       0
*POOL    ********       4        1      0    1       0          2       0
XC05     TESTP05       22        1     11    2       0          7       5
XP05     ********       5        2      0    1       0          1       1
DFHDB2020 01/17/98 15:45:27 IYKA4Z2G1  The display command is complete.

DB2ENTRY: Name of the DB2ENTRY, or “*COMMAND” for DSNC command calls, or “*POOL” for pool statistics.
PLAN: The plan name associated with this entry. Eight asterisks in this field indicate that this transaction is using dynamic plan allocation. The command processor transaction DSNC does not have a plan associated with it.
If a plan name associated with an entry is dynamically changed, the last plan name is the one put into use.
CALLS: The total number of SQL statements issued by transactions associated with this entry.
AUTHS: The total number of signon invocations for transactions associated with this entry. A signon does not indicate whether a new thread is created or an existing thread is reused. If the thread is reused, a signon occurs only if the authorization ID or transaction ID has changed.
W/P: The number of times that all available threads for this entry were busy. This value depends on the value of THREADWAIT for the entry. If THREADWAIT is set to POOL, W/P indicates the number of times the transaction overflowed to the pool. An overflow to the pool only shows up in the statistics for the individual DB2ENTRY, and is not reflected in the pool statistics.
If THREADWAIT is set to YES, this reflects the number of times that either the transaction had to wait for a thread (because the number of active threads had reached THREADLIMIT), or the transaction could not use a new thread TCB (because the number of TCBs in use running threads had reached TCBLIMIT).
HIGH: The maximum number of threads acquired by transactions associated with this entry at any time since the connection was started, that is, a high-water mark of threads.
Note: In releases of CICS before CICS® Transaction Server for OS/390®, Version 1 Release 2, the HIGH value also included the transactions forced to wait for a thread or those diverted to the pool. From CICS Transaction Server for OS/390, Version 1 Release 2 onwards, the HIGH value only represents threads created on the entry.
ABORTS: The total number of units of recovery which were rolled back. It includes both abends and syncpoint rollbacks, including syncpoint rollbacks generated by -911 SQL codes.
COMMITS: One of the following two fields is incremented each time a DB2 transaction associated with this entry has a real or implied (such as EOT) syncpoint. Units of recovery that do not process SQL calls are not reflected here.

1-PHASE: The total number of single-phase commits for transactions associated with this entry. This total does not include any two-phase commits (see the explanation for 2-PHASE). This total does include read-only commits as well as single- phase commits for units of recovery which have performed updates. A two-phase commit is needed only when the application has updated recoverable resources other than DB2.
2-PHASE: The total number of two-phase commits for transactions associated with this entry. This number does not include single phase commit transactions.