Global DDF activity (BSTATDR)
This topic describes the Global DDF activity section of the DB2 statistics detail report (BSTATDR).
------------------------- -------- ------- ------- -------
DBATS QUEUED-MAX ACTIVE 0 0.00 0.00 N/A
CONV DEALLOC-MAX THREADS 0 0.00 0.00 N/A
INACTIVE DBATS - CURRENT 0 N/A N/A N/A
INACTIVE DBATS - HWM 0 N/A N/A N/A
COLD START CONNECTIONS 0 0.00 0.00 0.00
WARM START CONNECTIONS 0 0.00 0.00 0.00
RESYNCHRONIZATION ATTEMPT 0 0.00 0.00 0.00
RESYNCHRONIZATION SUCCEED 0 0.00 0.00 0.00
CURRENT ACTIVE DBATS 0 0.00 0.00 0.00
MAX ACTIVE DBATS - HWM 0 N/A N/A N/A
MAX ALL DBATS - HWM 0 N/A N/A N/A
TYPE 1 CONN TERMINATE 0 0.00 0.00 0.00
CUR TYPE2 INACTIVE DBATS 0 0.00 0.00 0.00
TYPE2 INACTIVE DBATS HWM 0 0.00 0.00 0.00
CUR QUEUED TYPE2 INAC THD 0 0.00 0.00 0.00
REC QUEUED TYPE2 INAC THD 0 0.00 0.00 0.00
QUEUED TYPE2 INAC THD HWM 0 0.00 0.00 0.00
CURRENT DBATS NOT IN USE 0 0.00 0.00 0.00
DBATS NOT IN USE HWM 0 0.00 0.00 0.00
DBATS CREATED 0 0.00 0.00 0.00
POOL DBATS REUSED 0 0.00 0.00 0.00
NBR REQ DBA ACCESS 0 0.00 0.00 0.00
NBR REQ POOL ACCESS 0 0.00 0.00 0.00
NBR OF Q'D CLIENT(TCP/CLS) 0 0.00 0.00 0.00
NBR OF DBAT ACT PKG-BND 0 0.00 0.00 0.00
MAX OF DBAT ACT PKG-BND 0 0.00 0.00 0.00
The following table describes the fields in the Global DDF activity section.
Field | Description |
|---|---|
DBATS QUEUED—MAX ACTIVE | Number of times a DBAT thread was queued (QDSTQDBT) This counter indicates that a requester thread was queued because the serving system did not allow enough active remote threads. The tuning parameter is MAXDBAT in DSNZPARM. Tuning Tip: If this situation occurs often, increase MAXDBAT in DSNZPARM on installation panel DSNTIPE, reassemble, and restart DB2. |
CONV DEALLOC—MAX THREADS | Number of conversations deallocated due to ZPARM limit (QDSTQCRT) This situation occurs when the thread count from remote locations exceeds the sum of maximum active threads and inactive threads in DSNZPARM. Tuning Tip: If this situation occurs often, update the MAX REMOTE CONNECTED (CONDBAT) field in DSNZPARM on installation panel DSNTIPE, reassemble, and restart DB2. |
INACTIVE DBATS—CURRENT | Current number of inactive DBATs (QDSTQCIT) This counter reflects a snapshot count of inactive requester threads to this server. An inactive thread is a thread that is currently not executing but the VTAM connection has been kept intact on the assumption that this user will still be doing further work. |
INACTIVE DBATS—HWM | Maximum number of inactive DBATs (QDSTQMIT) This counter reflects the high-water mark of inactive threads. Tuning Tip: If the number is close to the value in DSNZPARM, consider increasing the number of inactive threads allowed (CONDBAT). |
COLD START CONNECTIONS | Number of cold start connections with all remote locations (QDSTCSTR) This reflects DB2 attempting to synchronize with a requester that has been cold-started (two-phase commit operations only). Tuning Tip: The primary significance of this number is that if it is nonzero, check whether any indoubt threads were left unresolved by the cold start. If so, the system programmer must issue -RESOLVE INDOUBT (COMMIT or ABORT) commands. |
WARM START CONNECTIONS | Number of warm start connections with all remote locations (QDSTWSTR) This counter indicates all connections made through normal restart processing (two-phase commit operations only). Tuning Tip: This number is of interest in determining that a problem does not exist. |
RESYNCHRONIZATION ATTEMPT | Number of resynchronization attempts with all remote locations (QDSTRSAT) This counter is incremented when communication is lost between a requester and server (two-phase commit operations only). Following restoration of communications, DB2 attempts to resynchronize all servers and requesters. Tuning Tip: A large number of resynchronization attempts indicates network difficulties or MVS problems. |
RESYNCHRONIZATION SUCCEED | Number of successful resynchronization attempts (QDSTRSSU) This counter is incremented when DB2 has successfully completed the resolution of indoubt processing after a communications failure. Tuning Tip: High numbers in this counter indicate VTAM problems that should be resolved with the VTAM system programmer. |
CURRENT ACTIVE DBATS | Current number of active database access threads (QDSTCNAT) |
MAX ACTIVE DBATS—HWM | Maximum number of active DBATs that existed (QDSTHWAT) |
MAX ALL DBATS—HWM | Maximum number of active and inactive database access threads (QDSTHWDT) |
TYPE 1 CONN TERMINATE | Number of connections that were terminated instead of being made type 1 inactive because the maximum number of type 1 inactive DBATs was reached (QDSTNITC) |
CUR TYPE 2 INACTIVE DBATS | Current number of inactive type 2 DBATs (QDSTCIN2) |
TYPE 2 INACTIVE DBATS HWM | Maximum number of inactive type 2 DBATs - high-water mark (QDSTMIN2) |
CUR QUEUED TYPE 2 INACT THD | Maximum number of type 2 inactive threads that were queued waiting for a database access thread (QDSTMQR2) |
REC QUEUED TYPE2 INAC THD | Number of receive requests on inactive connections, or new connections that have been queued to be serviced by a disconnected (pooled) DBAT |
QUEUED TYPE 2 INAC THD HWM | Number of queued RECEIVE requests for a type 2 inactive thread and the number of requests for new connections received after the maximum number of remote DBATs was reached (QDSTQIN2) |
CURRENT DBATS NOT IN USE | Current number of active database access thread slots that are not in use (QDSTNADS) |
DBATS NOT IN USE HWM | Maximum number of database access thread slots that were not in use because no processing was required to complete a queued receive request or to establish a new connection (QDSTMADS) |
DBATS CREATED | Number of requests that required a DBAT to be created to process the request (QDSTNDBA) |
POOL DBATS REUSED | Number of requests that were satisfied by assigning a pool thread to process the request (QDSTPOOL) |
NBR REQ DBA ACCESS | Number of requests that required a DBAT to be created to process the requests |
NBR REQ POOL ACCESS | Number of requests that were satisfied by assigning a disconnected (pooled) DBAT to process the requests |
NBR OF Q'D CLIENT(TCP/CLS) | Number of queued client connections |
NBR OF DBAT ACT PKG-BND | Number of active DBAT package binds |
MAX OF DBAT ACT PKG-BND | Maximum number of DBAT package binds |
Related topic