Collecting data for Db2 utility address spaces

To diagnose Db2 utility problems, collect Db2 utility address space and z/OS® system diagnostic data.

Before you begin

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

About this task

The following types of problems typically originate from the Db2 utility address space:
  • Virtual storage availability issues that are identified by z/OS system code 878 with reason code 10
  • Issues that are related to DFSORT SORT and MERGE functions of the utility
  • Utility data set access issues
  • Template code errors from the Db2 Utility parser

Procedure

Collect the following data to diagnose Db2 utility address space problems:
  • The utility job log
  • LOGREC data
  • SVC dump data sets that were generated by the error
  • The SYSLOG if a hardware-related issue is suspected
  • DFSORT diagnostic data that is written to the SORTDIAG DD statement. To write to SORTDIAG , add the following JCL to the utility job:
    //SORTDIAG DD DUMMY

What to do next

Depending on the problem, more information might be requested by IBM® Support. This information might include:
  • DDL for the table spaces, tables, and indexes
  • SMF trace data
  • Supervisor call (SVC) dump data sets that were generated by SLIP traps
  • Db2 diagnose reports, which can be generated by running the following command:
    DIAGNOSE DISPLAY MEPL (BEPL) report