Call Level Interface Guide and Reference

Detailed Trace File Format

Refer to the example trace file below. Note that the line numbers have been added for this discussion, and do NOT appear in the trace.

• Line 1: The build date and product signature is shown to aid IBM Service.

• Lines 2-3: First of a common two line sequence showing the arguments on input (--->) to the function call. Integer arguments may be mapped to a defined value like "SQL_HANDLE_ENV", output arguments are usually shown as pointers, with an "&" prefix.

• Lines 4-5: Two line sequence showing ouput (<---) results of the function call. Only output arguments are shown, and the return code on the second line following the (--->). Match this with the preceding input lines.

• Line 7: Example of an elapsed time on input. This is the time in the application between CLI function calls, shown in seconds. (Note: the granularity or accuracy of these timmings vary between platforms).

• Line 8: Example of an elasped time on output. This is the time in DB2 CLI spent executing the function.

• Lines 18-20: Both SQLDriverConnect() and SQLConnect() display the keywords set on both the input connection string and set in the db2cli.ini file.

• Line 23: The output statement handle is shown as 1:1, the first number represents the connection handle, the second the statement handle on that connection. This also applies to descriptor handles, but not to connection or environment handles, where the first number is always zero.

• Line 29: Example of SQL statement text for SQLPrepare().

• Line 43-44: Deferred arguments from SQLBindParameter() calls (lines 33 - 40). This is the data sent for each of the sql parameter markers (?) in the prepared statement (line 29).

• Lines 79-81: The ouptut from the SQLFetch() call. (iCol = Column, rgbValue = data in char format, pcbValue=Length).

• Line 110: SQLError() output, showing message text. The pfNativeError is either the DB2 SQLCODE or -9999 if the error originated from DB2 CLI instead of the database server.

• Line 123: Shows an unretrived error message. This is shown whenever a function is called using a handle which had a previous error, but was never retrieved by the application. It is effectively "lost" (to the application) at this point but is captured in the trace.

[ DB2 List of Books | Search the DB2 Books ]