SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
02-27-2008, 08:16 AM
| ||||
| ||||
 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      |
|
02-27-2008, 08:16 AM
| ||||
| ||||
| Re: DB2 ODBC Connection Expiration ron.tornambe@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 |
Linear Mode
