Collecting data for a DDF abend or DRDA exception

DDF abends and DRDA exceptions are indicated by DSNL messages. Information in messages DSNL032I and DSNL027I might indicate the reasons for the abend or exception. Collect generated dumps, trace records, and standard diagnostic information about Db2 and VTAM® to diagnose the DDF abends and DRDA exceptions.

Before you begin

To diagnose DDF problems, you must have the appropriate authorization to collect data from different z/OS® components.

Procedure

To collect diagnostic data for DDF abends and DRDA exceptions:

  1. Collect any supervisor call (SVC) dumps that were generated at the time of the abend.
  2. Collect the SYSLOG, which might contain messages that indicate the source of the problem. Specifically, collect DSNL messages.
  3. Collect the JES lob log, which might contain messages that indicate the source of the problem. Specifically, collect DSNL messages.
  4. Collect the LOGREC, which might contain messages that indicate the source of the problem.
  5. Collect SMF Type 102 data with IFCID 0191 and 0192 from a Db2 statistics trace. Information in message DSNL032I indicates the sequence number of the trace record to capture.
  6. To capture trace records for exceptional conditions while Db2 is running:
    -START TRACE(STAT) CLASS(4)