I recently came across a scenario where GSKit trace was not getting generated in a Db2 Purescale environment.
What works in a regular EE instance doesn't work in Purescale environment, you will need to temporarily add the export to the sqllib/db2profile file.
The reason is that Purescale node (even though logical node) are treated as physical node internally so it does not pick up the environment variable like the EE.
Here is an example:
1. Update the sqllib/db2profile, add the following lines to the end of the file: (Remove it once you are done with the trace)
2. db2set DB2ENVLIST="GSK_TRACE_FILE GSK_TRACE_FILE_SIZE"
3. db2stop and db2start
4. db2 activate db xxx, db2 connect to xxx -> you will see the /tmp/gsktrace.out file created.