Subsystem Support Manager Statistics Detail
This panel shows detailed information about DB2 activity during a selected report interval, including statistics related to Create Thread, Signon, Commit, and abnormal termination activity.
________________ ZHSMD VTM O2 V540.#P DA41 11/06/13 11:40:01 2
> Help PF1 Back PF3 Up PF7 Down PF8
>
> Enter a selection letter on the top line.
>
> *-SUBSYSTEM SUPPORT B-BIND C-BUFFER POOL D-GROUP BP
> E-DISTRIBUTED DATABASE F-EDM POOL G-LOG MANAGER H-OPEN/CLOSE
> I-SQL/RID/PARALLEL/PROC J-LOCK/CLAIM/DRAIN K-GLOBAL LOCK L-DB2 COMMANDS
> M-THREAD HISTORY
===============================================================================
> SUBSYSTEM SUPPORT MANAGER STATISTICS DETAIL
HSMD
+ Collection Interval: 1 min Start: 11/06 11:36
+ Report Interval: 1 min Combine Level: NONE End: 11/06 11:37
+
+ High Water Mark for IDFORE = 5
+ High Water Mark for IDBACK = 20
+ High Water Mark for CTHREAD = 17
+
+ INTERVAL /MINUTE
+ QUANTITY ( 1)
+ -------- -------
+ Identify Requests 0 .00
+ Signon Requests 0 .00
+ Create Thread Requests 0 .00
+ Create Thread Waits 0 .00
+ Terminate Thread Requests 0 .00
+
+ Single Phase Commit Requests 0 .00
+ Read Only Commit Requests 53 53.00
+ Commit Phase 1 Requests 0 .00
+ Commit Phase 2 Requests 21 21.00
+ Abort Requests 0 .00
+ Total Commit Requests 74 74.00
+
+ Indoubt Threads 0 .00
+ Indoubts Resolved 0 .00
+ Abends Detected - End of Task 0 .00
+ Abends Detected - End of Memory 0 .00
+
+ High Water Mark for IDFORE 0 .00
+ High Water Mark for IDBACK 0 .00
+ High Water Mark for CTHREAD 0 .00
===============================================================================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
- Collection Interval
- The time interval specified for the collection of near-term history data. This unit of time was specified when the Near-Term History Data Collector was started.
- Start
- The start time of the interval currently displayed.
- Report Interval
- This field determines the report interval. It is set on the Near-Term History Report Option panel.
- Combine Level
- This field reflects the selected combine level.
If Combine Level is NONE, the report interval is the same as the collection
interval. Possible values:
- HOURLY
- Data will be reported in hourly intervals.
- NONE
- Data will be reported in the time unit specified by the collection interval.
- End
- The end time of the interval currently displayed.
- Identify Requests
- Successful connections to DB2 from an allied address space.
- Signon Requests
- Successful requests to identify a new user for IMS or CICS®. Thread Signon processing is applicable only in CICS-DB2 and IMS-DB2 attachment environments.
- Create Thread Requests
- Successful Create Thread requests.
- Create Thread Waits
- Create thread requests that had to wait because no thread was available.
- Terminate Thread Requests
- Successful thread terminations.
- Single Phase Commit Requests
- Successful commit requests that took place in a single-phase commit environment, for example, TSO.
- Read Only Commit Requests
- A read-only commit occurs if no DB2 resources have been changed since the last commit for IMS or CICS applications. Db2 performs both phases of the commit process during phase 1.
- Commit Phase 1 Requests
- Commit phase 1 requests in a two-phase-commit environment, for example, CICS and IMS.
- Commit Phase 2 Requests
- Commit phase 2 requests in a two-phase-commit environment, for example, CICS and IMS.
- Abort Requests
- Events that resulted in successfully backing out a unit of recovery.
- Total Commit Requests
- Includes single-phase, read-only, and phase 2 commit requests.
- Indoubt Threads
- The number of indoubt threads. A thread goes indoubt when a failure occurs between commit phase 1 and commit phase 2.
- Indoubts Resolved
- Successful resolutions, either automatic or manual, of indoubt threads.
- Abends Detected - End of Task
- Tasks that abended while connected to DB2.
- Abends Detected - End of Memory
- The number of times a non-DB2 address space was deleted by MVS while connected to Db2.
- High Water Mark for IDFORE
- The maximum number of users that are identified to DB2 from TSO foreground at the same time.
- High Water Mark for IDBACK
- The maximum number of concurrent connections identified to DB2 from batch.
- High Water Mark for CTHREAD
- The maximum number of allied threads that are allocated concurrently.