CICS DB2: Resource statistics - request information

The request information gives details of how many requests of various types have been performed against each DB2ENTRY.

Table 1. CICS DB2: Resource statistics - request information
DFHSTUP name Field name Description
DB2Entry Name D2R_DB2ENTRY_NAME is the name of the installed DB2ENTRY

Reset characteristic: not reset

 

Call Count D2R_CALLS is the number of SQL calls made using this DB2ENTRY. If you are using PACKAGESET support for cloud applications, this number includes the number of EXEC SQL SET CURRENT PACKAGESET commands issued by DFHD2SPS on behalf of the application.

Reset characteristic: reset to zero

 

Signon Count D2R_SIGNONS is the number of DB2® signons performed for this DB2ENTRY.

Reset characteristic: reset to zero

 

Partial Signon D2R_PARTIAL_SIGNONS is the number of DB2 partial signons performed for this DB2ENTRY.

Reset characteristic: reset to zero

 

Commit Count D2R_COMMITS is the number of two phase commits performed for units of work using this DB2ENTRY.

Reset characteristic: reset to zero

 

Abort Count D2R_ABORTS is the number of units of work using this DB2ENTRY that were rolled back.

Reset characteristic: reset to zero

 

Single Phase D2R_SINGLE_PHASE is the number of units of work using the DB2ENTRY that used single-phase commit, either because they were read-only UOWs, or because DB2 was the only recoverable resource updated in the UOW.

Reset characteristic: reset to zero

 

Thread Create D2R_THREAD_CREATE is the number of create thread requests made to DB2 for threads of this DB2ENTRY.

Reset characteristic: reset to zero

 

Thread Reuse D2R_THREAD_REUSE is the number of times CICS® transactions using the DB2ENTRY were able to reuse an already created DB2 thread.

Reset characteristic: reset to zero

 

Thread Terms D2R_THREAD_TERM is the number of terminate thread requests made to DB2 for threads of this DB2ENTRY.

Reset characteristic: reset to zero

 

Thread Waits/Overflows D2R_THREAD_WAIT_ OR_OVERF is the number of times all available threads in the DB2ENTRY were busy and a transaction had to wait for a thread to become available, or overflow to the pool and use a pool thread instead.

Reset characteristic: reset to zero

 



dfht3_stats_db2_resource_request.html | Timestamp icon Last updated: Monday, 5 June 2017