Call Level Interface Guide and Reference

Locating the Resulting Files

If you used a fully qualified filename with the TRACEFILENAME keyword, you should have no problem locating the file. If you used a relative pathname, it will depend on what the operating system considers the current path of the application.

If you used a pathname instead of a filename with the TRACEPATHNAME keyword, you will need to check the directory for a set of files created with the name set to the process id of the application and an extension that is a sequence number for each unique thread (eg. 65397.0, 65397.1, 65397.2 etc.). The file date and timestamp can be used to help locate the relevant file.

If you used a relative pathname, it will depend on what the operating system considers the current path of the application.

If there is no output file:

• Verify that the keywords are set correctly in db2cli.ini.
• Ensure the application is restarted. Specifically, SQLAllocEnv() must be called to read the db2cli.ini file and initialize the trace.
• Ensure the application has write access to the specified filename.
• Check if the DB2CLIINIPATH environment variable is specified. This environment variable changes the location from which the db2cli.ini file will be read.
• ODBC applications will not access the IBM CLI/ODBC/JDBC Driver until the first connect call. No trace entries will be written to the file until the application makes this connect call. See ODBC Driver Manager Tracing for more details.