Collecting data for a Db2 hang

If Db2 seems to hang while processing, you can collect initial diagnostic information about your environment.

Before you begin

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

Procedure

To collect diagnostic data for Db2 hang problems:

  1. Issue a DISPLAY THREAD command to display threads in a long-term suspend state. Refer to Db2 commands for troubleshooting for information about the options of the DISPLAY THREAD command to diagnose thread waits.
  2. Capture a supervisor call (SVC) dump for your Db2 environment. Include all Db2 address spaces in the JOBLIST of your DUMP command. Also, include the address space of any jobs in a long-term suspend state that is waiting for Db2. In a data sharing environment, create a SLIP trap to capture address spaces from remote Db2 members.
  3. Collect the SYSLOG, which might contain messages that indicate the source of the problem. Ensure this log contains information about the oldest waiting job.
  4. Collect the LOGREC, which might contain messages that indicate the source of the problem. Ensure this log contains information about the oldest waiting job.
  5. Collect the JES job logs for key Db2 address spaces.