it seems to me that the server jobs will end up maintaining open
data paths to all the files in both systems

Fair point if you're using RPG stored procs, or some other thing that
keeps the ODP lying around indefinitely. But for your average SQL
statement you should be fine. Yes, your right that the reused job may
not have the file open, but it will then open the file and run the
statement. IIRC, the paths will be closed eventually anyway. You could
also set a low lifetime on the pool and discard connections after 5
minutes, or something on that order.

To me it comes down to not wanting to rely on _any_ state on the
server-side connection. Yes, there are certain things you can't avoid,
like ODPs, but the system should be able to handle that.

-Walden


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.