> > I don't see why this would make any difference at all, > > since the closing CFTRANSACTION tag marks the end of > > the transaction, > > Yes, we agree. Apparently this is not enough, though. > According to our IBM contact we need additional housekeeping > beyond what happens with CFTRANSACTION. We need to properly > initiate and terminate the DB2 threads for the stored > procedure(s) so they aren't left hanging. This is in > addition to CF's built-in thread management. She's talking > about DB2 threads.
We're talking about server threads, right, not client threads? Honestly, this is the strangest thing I've ever heard, I think. You might want to ask your IBM contact how is this normally handled in other ODBC client applications. If she can provide some code examples for other languages, it might be a helpful start. But really, this sounds like something that should be handled by either the server itself, or the database client layer provided by IBM. > I need to find a good resource for CF and DB2 cursor > management . . . I wouldn't limit the search to something like that - any other high-level ODBC client (like ASP) should provide good examples. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
