Capturing ODBC diagnostic trace information in z/OS

Use the ODBC diagnostic trace only under the direction of IBM® Support.

Procedure

To capture ODBC diagnostic trace information in z/OS®:

  1. Activate the diagnostic trace by performing one of the following actions:
    • Specify DIAGTRACE=1 in the Db2 ODBC initialization file.
      If you activate the diagnostic trace by using the DIAGTRACE keyword in the initialization file, you must also allocate a DSNAOTRC data set in your job or TSO logon procedure. You can use one of the following methods to allocate a DSNAOTRC data set:
      • Specify a DSNAOTRC DD statement in your job or TSO logon procedure.
      • Use the TSO/E ALLOCATE command.
      • Use dynamic allocation in your ODBC application.
    • Issue one of the following ODBC diagnostic trace commands:
      • DSNAOTRC command for non-XPLINK applications
      • DSNAOTRX command for 31-bit XPLINK applications
      • DSNAO64T command for 64-bit applications
    Recommendation: When tracing 64-bit applications, consider specifying a diagnostic trace buffer size that is up to 10% bigger than what you would specify for 31-bit applications. If you activated the trace by specifying DIAGTRACE=1 in the ODBC initialization file, specify this buffer size with the DIAGTRACE_BUFFER_SIZE keyword in the initialization file. If you activated the trace by using a diagnostic trace command, specify this buffer size as a parameter of that command.
  2. Stop, dump, or format the trace as needed by using the appropriate ODBC diagnostic trace command with the relevant options or by changing the values of the appropriate keywords in the ODBC initialization file.