|
No, the same job but no open files. It's the only odbc job running on
the iSeries. It's also very dependant on how the connection is made, and maintained. I believe the default is to lazy-close the connection, so it's possible the connection was still open the first time, but actually closed the second time. Also, if you're using connection pooling it's possible the connection wasn't closed at all the first time. Finally, SQL may have kept the files open the first time for performance reasons, but decided it didn't need to do that the second time. Not to ask a silly question, but other than morbid curiosity, why do you care that the files were left open? The way the query is implemented, and even how the connection works are subject to change at any time if IBM cares to change the code, and probably even is effected by the general load on the system, and available memory, disk performance, etc. -Walden
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.