trace jdbc connection DB2 on z/OS

Fons Maathuis (25●4●17) | asked Jan 08 '18, 10:45 a.m.

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.

Even when in idle, RTC keeps using to much resources, so we're trying to determine the problems.

JDBC has a possibility to trace the connection, but how can I use that in my properties on RTC.

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

permanent link

Jean-Bernard Curmi (141●6●2) | answered Jan 10 '18, 4:13 a.m.
JAZZ DEVELOPER

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;

Fons Maathuis selected this answer as the correct answer

Comments

Fons Maathuis commented Jan 10 '18, 5:01 a.m.

also found a way to see what happens in DB2, had to change the log4j.properties files. Uncomment a few lines, all is documented in the log4j-files.

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

It's all about the answers!

Related questions

trace jdbc connection DB2 on z/OS

Accepted answer

Your answer