Take a look at the IBM.Data.DB2.iSeries.iDB2Command.Dispose() method.
Looks like there are some destructor calls within Dispose() to unmanaged
cwbxxx libs. Explicitly calling dispose and GC.SuppressFinalize(cm)
might be helpful instead of waiting for it to fall out of scope.
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Walden H. Leverich
Sent: Thursday, September 24, 2009 10:53 AM
To: Midrange Systems Technical Discussion
Subject: RE: Occasional .Net
Data access is wrapped in (an older version of) our generic data access
code. Each request is a new connection (pooling not withstanding). For
What do you mean "out of proc iis situation"?