Re: Persistent Sessions in DB connection for QZDASOINIT, implemented by Nathan

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