Collecting data for problems with DFSMS VSAM data sets

If you encounter problems with DFSMS VSAM data set manipulation, you can collect initial diagnostic information about your environment. DSNP messages usually indicate that the Db2 data space 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. DFSMS VSAM error messages often accompany the Db2 errors and can help in problem determination.

Procedure

To collect diagnostic data if DSNP messages indicate a problem with DFSMS VSAM data set manipulation:

  1. Collect the SYSLOG, which might contain messages that indicate the source of the problem.
  2. Collect the LOGREC, which might contain messages that indicate the source of the problem.
  3. Collect the JES job log for the ssnmMSTR and any allied agent address space.
  4. Collect any supervisor call (SVC) dump that was generated with abend code 04E and reason code 00D7xxxx for your Db2 environment.
  5. For a data set extend failure that is identified by message DSNP007I, collect the following data:
    1. Collect IDCAMS LISTCAT extent information for the target linear data set.
    2. Collect Db2 Statistics CLASS 3 trace with IFCID 0258 with information about the data set extend request.