Collecting data for a problem between a DRDA requester and server
Db2 trace data can be used to diagnose problems with the distributed data facility (DDF).
Before you begin
To diagnose DDF problems, you must have the appropriate authorization to collect data from different z/OS® components.
Procedure
Re-create the problem scenario while the generalized trace facility (GTF) and the following traces are started. Stop GTF after re-creating your scenario.
Issue the appropriate START TRACE command for your situation:
- Start the Db2 performance
trace:
-START TRACE (PERFM) CLASS(16) IFCID(165,180,184) - For SQL problems, add class 3 to the performance trace:
-START TRACE (PERFM) CLASS(3) - For DRDA exceptions,
start statistics trace with class 4:
-START TRACE (STAT) CLASS(4)
- For authorization issues, start an audit trace with class
1 and 7:
-START TRACE (AUDIT) CLASS(1,7)