The purpose of the trace is to display the sequence of calls, the input and output arguments and the return code for each function called. The trace is intended for people familiar (or looking to become familiar) with the DB2 CLI or ODBC function calls. Two things that are useful for anyone is the the SQL statement text being executed and any error messages that the application may not be reporting.
To locate:
Search the trace file for the strings "SQLExecDirect" and "SQLPrepare", you will find the SQL Statement on the same line that contains the text and the "--->" input arrow (although your editor may wrap the line).
Search the trace file for "SQLError", the message text will be shown on the line that contains the string and the output arrow "<---".
Search for "Unretrieved error message=" This indicates that a previous call got an SQL_ERROR or SQL_SUCCESS_WITH_INFO return code, but that the application did not query for the error information.
| Note: | An application may expect some error messages, you should look at all the error messages in the trace file and try to determine the serious ones. |