Reporting distributed data

OMEGAMON for Db2 Performance Expert can report activities that are associated with distributed work, where one Db2 subsystem accesses data from other DB2 subsystems.

DB2 uses the Distributed Data Facility (DDF) to allow an application program that is connected to one Db2 system to access data at a remote Db2 system, or any other relational database management system (DBMS) that supports DRDA.

OMEGAMON for Db2 Performance Expert can produce reports for a single DB2 location, or for a number of different Db2 host locations, when data is present. You can logically concatenate data sets from several locations in your JCL to produce a multilocation report. The data is then reported separately for each subsystem and ordered by location in alphabetic order.

When work is distributed across locations, the report shows activity at the reported location only.

The following information is reported for every location:
  • Nondistributed transactions, this means, the allied threads at the reporting location.
  • Local activity for distributed transactions that originate at the reporting location, this means, the allied-distributed threads at the reporting location without the corresponding DBATs at other locations.
  • Remote activity performed at the reporting location as part of distributed transactions originating at other locations, this means, the DBATs at the reporting location.
Depending on the type of report, further detail information is reported.
  • The Statistics report set shows following information in the Global DDF and the DRDA Remote Locations blocks of the report:
    • Distributed Data Facility (DDF) address space CPU times
    • Statistics for each DB2 remote location for Db2 host subsystems (MVS™, OS/390®, and z/OS®)
    • Aggregate Statistics for all locations that use DRDA
    • Other, nonlocation-specific DDF information
  • The Accounting report set shows information for specific threads that participate in distributed activity. Information is shown for both requester locations and server locations. The reports show, for example, elapsed times spent at the server site and the number of transactions, conversations, SQL statements, rows, messages, and bytes sent from the requester and received by the server. This information is reported in the Distributed Activity block of the report.
  • The SQL Activity report set shows all SQL data within threads. SQL statements are reported at the location where they were executed, both at the requester location and the server location.
  • The Explain report set can show information for packages that are bound at a remote location.

    If a list of plans to be explained contains a remotely bound package on a Db2 host system, EXPLAIN automatically connects to the server and explains the remote package. Alternatively, you can specify the server location to which EXPLAIN is to connect and the plans and packages that you want explained.