Collecting data for data set access problems

If you encounter data set open, allocation, reading, writing, or synchronization problems, collect diagnostic data from a time period when the problem occurred. DSNB messages usually indicate that the Db2 buffer manager subcomponent encountered a problem.

Before you begin

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

About this task

Diagnosing data set access problems requires IBM® Support expertise. Often, DFSMS VSAM errors are involved.

Procedure

To collect diagnostic data if DSNB messages indicate a corruption or inconsistency problem:

  1. Collect Db2 archive log data sets from all Db2 members to the last point of consistency. Also, collect the corresponding consistent REORG or IMAGE COPY data sets.
  2. Collect the SYSLOG, which might contain messages that indicate the source of the problem.
  3. Collect the LOGREC, which might contain messages that indicate the source of the problem.
  4. Collect the JES job log for the ssnmMSTR address space.
  5. Collect any supervisor call (SVC) dump that was generated with abend code 04E and reason code 00C2xxxx for your Db2 environment.