If users in more than one environment cannot issue SQL statements

This situation is when users of two or three of the attachment facilities cannot complete transactions, but Db2 is not hung; Db2 still responds to commands, or one attachment facility still operates normally.

Procedure

  1. If the z/OS® GTF trace facility is not active, issue the z/OS START GTF command with the USR and TIME=YES options.
  2. Verify that dump data sets are available.
  3. Issue the z/OS DUMP command to dump the Db2 address spaces (database services, system services, distributed data facility address space (for distributed processing only) and any user address spaces) and the IRLM address space. Many large dumps are produced that can help to diagnose the problem if other methods fail.
  4. Determine if the problem is a WAIT or LOOP.
    • Examine the trace tables: GTF, Db2, TSO, GRS, CICS®, IMS attachment facility, or IMS. Be aware of any repeating patterns, which might indicate a LOOP.

      To use the GRS (global resource serialization) trace for a stand-alone dump, use the GRSTRACE keyword when the dump is printed.

    • Investigate what some users were doing before the problem occurred. If several users were doing the same thing, such as trying to access one resource, this might indicate a WAIT.
  5. Add WAIT or LOOP to the keyword string. If unsure about which is appropriate, create two strings, one with each keyword. Turn to Searching the IBM Support site for known problems and solutions.
      (free format):
      5740XYR00 R111 WAIT
      5740XYR00 R111 LOOP
      (structured format):
      PIDS/5740XYR00 LVLS/111 WAIT
      PIDS/5740XYR00 LVLS/111 LOOP