470,591 Members | 2,085 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,591 developers. It's quick & easy.

DB2 ODBC Connection Expiration

I am working on an audit trail mechanism for an MS-Access application
that connects to a DB2 backend. We need the APPLICATION_ID to remain
constant until the application is terminated. It appears that DB2
connections expire after some duration and new ones are created when
needed by the application. Is there a way to confiure the connection
expiration so it persists until the application is terminated?

TIA,
Ron in SF

Sep 20 '06 #1
1 1378
ro**********@bunkerhill.com wrote:
I am working on an audit trail mechanism for an MS-Access application
that connects to a DB2 backend. We need the APPLICATION_ID to remain
constant until the application is terminated. It appears that DB2
connections expire after some duration and new ones are created when
needed by the application. Is there a way to confiure the connection
expiration so it persists until the application is terminated?
The application-id will not be changed unless the client disconnects from
DB2. My guess is that your ODBC driver (in case you are not using DB2 CLI
natively) or your client application performs the disconnect - maybe
MS-Access? You should have a look at these configurations.

--
Knut Stolze
DB2 Information Integration Development
IBM Germany
Sep 20 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by Sean Anderson | last post: by
5 posts views Thread by SerGioGio | last post: by
11 posts views Thread by DJJ | last post: by
4 posts views Thread by Andreas Lauffer | last post: by
5 posts views Thread by Alec | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.