Gathering diagnostic information

Before you report a problem with Db2 Table Editor to IBM® Software Support, you need to gather the appropriate diagnostic information.

Procedure

Provide the following information for all Db2 Table Editor problems:
  • A clear description of the problem and the steps that are required to re-create the problem
  • All messages that were issued as a result of the problem
  • Product release number and the number of the last program temporary fix (PTF) that was installed
  • The version of Db2® that you are using and the type and version of the operating system that you are using
Provide additional information based on the type of problem that you experienced:
For online abends, provide the following information:
  • A screen capture of the panel that you were using when the abend occurred
  • The job log from the TSO session that encountered the abend
  • The job log from the server
  • A description of the task that you were doing before the abend occurred
For errors in batch processing, provide the following information:
  • The complete job log
  • Print output
  • Contents of the data sets that were used during the processing
For problems with the Tools Customizer trace data set name:
If you cannot allocate the trace data set, the trace data set runs out of space, or IBM Software Support asks for it, you will need to identify the name of the trace data set. The name of the trace data set depends on the prefix setting in the TSO profile. To identify the name of the trace data set, you must know the prefix setting.
  • If PREFIX is set, the name of the trace data set is prefix.CCQ.TRACE, where prefix is the TSO prefix that you specified in the profile.
  • If NOPREFIX is set, the name of the trace data set is user_ID.CCQ.TRACE, where user_ID is your TSO user ID.