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.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[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
example http://code.midrange.com/60ca85629c.html

What do you mean "out of proc iis situation"?


This thread ...


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

This mailing list archive is Copyright 1997-2019 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].