Distributed activity

The Accounting trace provides insights to activities among distributed DB2 subsystems as well as non-DB2 requestors.

OMEGAMON for Db2 Performance Expert supports communication between:

  • DB2 for z/OS® subsystems
  • DB2 for z/OS subsystem and non-DB2 requesters, such as SQL/DS, or ORACLE

For detailed information about the communication between these systems, produce an Accounting trace.

For communication between two DB2 subsystems, the Accounting trace provides you with information about the requester locations (for DBATs) and the server locations (for requester threads).

For communication between a DB2 subsystem and a non-DB2 for z/OS requester, OMEGAMON for Db2 Performance Expert can only present performance data on DBATs. However, the Accounting trace helps you to identify the requester. It supplies the identifier and release level of the requester involved. For requesters from DB2 on other platforms also provides the client platform, application name, authorization ID, and a user-supplied part. If possible, OMEGAMON for Db2 Performance Expert uses the first eight bytes of the application name to identify the DBAT. If it is not possible to show the DBAT application name, the plan name is shown as DISTSERV. When DISTSERV is shown, you can use the MAINPACK identifier to distinguish DBATs.

Accounting trace records are affected by the DB2 subsystem parameter ACCUMACC, which controls whether and when DB2 Accounting data is accumulated by the user for DDF and RRSAF threads. A parameter value of 2 or greater causes Accounting records to roll up into a single record every n occurrences of the user on the thread. These values can be set by DDF threads by Server Connect and Set Client calls, and by RRSAF threads by RRSAF SIGN, AUTH SIGNON, and CONTEXT SIGNON functions. When roll-up occurs, the values of some fields shown in Accounting reports and traces lose their meanings because of the accumulation. Thus, these fields are marked as N/P or N/C for derived fields. For a list of affected fields, see Fields affected by roll-up during distributed and parallel tasks.