|
May be this is related with the number of cursors that remains opened in the de QZDASOINIT job. The OS/400 does not close (hard close) the cursor that you close, really it does a soft close and retain the cursor open for reuse. You can control this behavior with the parameters OPEN_CURSOR_THRESHOLD and OPEN_CURSORCLOSE_COUNT in a QAQQINI file. On Thu, 2005-11-10 at 12:22 -0600, TitanRebel wrote: > In many QZDASOINIT jobs, we find the PWS0083 message: > > Additional 16 megabytes of storage allocated for this job. > > Is this message "normal", or does it point to a memory leak. We are > using our own implementation of connection pooling, and some JDBC > connections can potentially stay in memory and used over and over for > quite a long time (days). Is this a problem? > > Do we need to close and open new JDBC connections more frequently to > allow these jobs to release the resources (I'm just assuming that they > would release the resources after closing the JDBC Connection)? > > Thanks, > > Ken
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.