# Detailed Logging - CONNX JDBC

**URL:** <https://techcommunity.softwareag.com/t/detailed-logging-connx-jdbc/101156>\
**Category:** Forum\
**Tags:** Adabas-Natural, Adabas, Adabas-Add-on-Products, SQL-Access, Mainframe-Integration, CONNX\
**Created:** [August 6, 2012, 9:30pm UTC](https://techcommunity.softwareag.com/t/detailed-logging-connx-jdbc/101156 "2012-08-06T21:30:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Min\_Chai](https://avatars.discourse-cdn.com/v4/letter/m/71c47a/32.png) [@Min\_Chai](https://techcommunity.softwareag.com/u/Min_Chai)\
**Post date:** [August 6, 2012, 9:30pm UTC](https://techcommunity.softwareag.com/t/detailed-logging-connx-jdbc/101156/1 "2012-08-06T21:30:23Z")

</div>

We are trying to conduct some assessment on the application that use CONNX. Specifically, I like to know if there is any more detailed logging of the JDBC server I can have aside from the level 1 and 2 that I can configure with the Configuration Manager.

I think that when an SQL insert comes to the CONNX JDBC Server, the sql insert is converetd into Adabas commands by the sql gateway client running in the JDBC server space. Is there a way I can figure out

1. when the SQL Gateway client issue each of the Adabas command to the SQL Gateway server on the mainframe
2. when the command reaches the Adabas SQL Gateway server on the mainframe.
3. when the SQL Gateway server on the mainframe sends the command over to Adabas.

Adabas processes the command very quickly so I have no issue there.

What can I do to gather the statistics I need?

Thanks,  
min

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [August 7, 2012, 9:05am UTC](https://techcommunity.softwareag.com/t/detailed-logging-connx-jdbc/101156/2 "2012-08-07T09:05:46Z")

</div>

The following diagnostic information is available:

1. Execution Workplan  
by adding the SQL Extension {statistics} to the statement

2. JDBC Server Logging  
DEBUGLEVEL 0,1 and 2  
DEBUGVERBOSE 0 and 1

3. Data Server Logging for Adabas  
ADA\_DEBUG\_TRACE\_MASK settings display the contents of the Adabas buffers

Should further statistic functions be required, please contact SAG Support

Thanks,  
Rick

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\
**Post date:** [April 2, 2021, 3:02pm UTC](https://techcommunity.softwareag.com/t/detailed-logging-connx-jdbc/101156/3 "2021-04-02T15:02:16Z")

</div>