🚀 go-pugleaf

Chris, I have just been experimenting with the CLI trace after your note.  The
instructions we gave were to use the line:
 tracefilename=xxx
in your DB2CLI.INI file.

There is another option, which is to use:
 tracepathname=c:\sqllib                (specify whatever directory you want on whatever
drive you want)

We suggested "tracefilename" in our instructions because it seemed simpler.  After
experimenting with it myself, I found the same problems as you did.  However, if you
switch to "tracepathname" and then reboot, these problems should go away. Once you do
that, you can just turn the trace on and off in DB2CLI.INI and the trace will start and
stop without even stopping and starting DB2. I was also able to edit the trace file while
DB2 was still running. The only thing I can't do is erase the file.  You wont' be able to
erase a trace file until all the DB2 processes using it are terminated.  Unfortunately, I
can't offer any advice on how to do that better than you described in your note.

When you use "tracepathname", a separate trace file will be created for each thread. All
the files will have generated names. On my NT machine, these names are all numeric (for
example: 263.0, 263.1). They should be pretty easy to find in the directory you specify.
You just have to figure out which one contains the trace statements you are looking for.