Subsystem reports
The Subsystem reports are produced from database subsystem accounting data stored in SMF files. (Note that the DB2® report also processes CMF performance class data whereas the WebSphere® MQ and OMEGAMON® reports do not.)
- DB2
- Correlates CICS® CMF performance
class (SMF 110) records and DB2 accounting
(SMF 101) records by network unit-of-work to produce a consolidated
and detailed view of DB2 usage
by your CICS systems. The DB2 report enables you to view CICS and DB2 resource usage statistics together in a single
report. The DB2 List report
shows detailed information of DB2 activity
for each transaction. The DB2 Summary
reports summarize DB2 activity
by transaction.
See DB2 report.
- WebSphere MQ
- Processes WebSphere MQ
accounting (SMF 116) records to provide comprehensive performance
analysis and resource usage for your CICS transactions
that use MQ. The WebSphere MQ List report provides a trace of MQ accounting records, reporting the comprehensive performance contained in subtype 0, 1 and 2 records. The WebSphere MQ Summary report provides two summarized views of your MQ transactions:
- Summary by CICS Transaction ID, showing the MQ system and queue resources use
- Summary by WebSphere MQ Queue name, showing the Transactions they service and resources used
- OMEGAMON
- Processes OMEGAMON XE
for CICS (SMF
112) records to produce a detailed view of how CICS transactions use the following types of
database management system (DBMS): Adabas, CA-Datacom, CA-IDMS, and
Supra.
For each type of DBMS, you can request up to three reports:
- A List report, showing database usage for each transaction.
- A Transaction Summary report, showing database usage summarized by transaction ID.
- A Database Summary report, showing database usage summarized by database.
The information in each report varies depending on the DBMS, but typically includes elapsed times and counts for each method that is used by transactions to access a database, such as read, write, add, update, and delete.
See OMEGAMON reports.