QUESTION POSED ON: 29 January 2008
My company is developing a Web application (.NET) and uses Webservices to connect to iSeries.
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?
|
