trace jdbc connection DB2 on z/OS
We do have big problems using RTC with DB2 on z/OS. It seems like RTC keeps firing request to the database, which use up a lot of CPU. Apparently for each request RACF is consulted, which also leads to a lot of CPU.
jdbc:db2://localhost:50000/sample:traceDirectory=c:\temp;traceFile=jcctrace.log;traceFileAppend=false;traceLevel=-1; should do the trick, but where to put it? <o:p> </o:p>
Accepted answer
You can do that by editing your teamserver.properties files in
installationDirectory/server/conf/jts and
installationDirectory/server/conf/ccm
append
traceDirectory=c:\temp;traceFile=jcctrace.log;traceFileAppend=false;traceLevel=-1;
to your com.ibm.team.repository.db.jdbc.location propertie
ie replace
com.ibm.team.repository.db.jdbc.location=//ipAddress:ipPort/location:user=jazzDBuser;password={password};
by
com.ibm.team.repository.db.jdbc.location=//ipAddress:ipPort/location:user=jazzDBuser;password={password};traceDirectory=c:\temp;traceFile=jcctrace.log;traceFileAppend=false;traceLevel=-1;