Everything was OK, but recently we noticed that QZDASOINIT jobs are remaining active (with several locks) in the...
QUSRWRK subs, despite the connections being closed.
I've done some investigation and found out that the pooling property could have something to do with this.
Pooling = true gives us the current scenario; pooling = false gives us the desired scenario, as the QZDASOINIT jobs are terminated once the browser closes, but all the connections are extremely slow.
What we want is this scenario:
Each connection to iSeries creates an QZDASOINIT job and terminates it when is not needed anymore, but the connection is as fast as if we had pooling = true.
Is there any way to do this via .net code, connectionstring, or iSeries configuration?
Good luck with it.
Dig Deeper on DB2 UDB (universal databases)
Related Q&A from Jim Mason
Java to Excel with the AS400 may be attractive, but if you have complex VBA macros in Excel, the JDBCODBC bridge will not work well for you. A better... Continue Reading
There are a couple of options for accessing AS/400 data, from the old way using Client Access ODBC drivers, to Java, to a new application from Groovy. Continue Reading
One user writes, "How can I connect WebSphere on my iSeries to a DB2 database on an AIX machine? We've tried a number of different methods ... Continue Reading