> We are using CF 5.0 to call stored procedures in mainframe
> DB2.
>
> ...
>
> This works fine except that under load we get abends on the
> stored procedure unless we turn off the 'stay resident'
> parameter in DB2 that keeps the stored procedure code
> resident in memory. Of course this affects performance.
>
> IBM seems to think this is a commit problem, so we are
> playing around with the nested <cftransaction action="commit" />
> tag to see if it helps us to avoid the abends.
>
> How would you use the action=commit parameter with our code
> shown above? Where would you insert this code?
I don't see why this would make any difference at all, since the closing
CFTRANSACTION tag marks the end of the transaction, at which time all
changes should automatically be committed if the transaction succeeded, but
stranger things have happened.
You might try putting it right before your closing CFTRANSACTION tag:
<cftransaction>
<cfstoredproc ...>
...
</cfstoredproc>
<cftransaction action="commit" />
</cftransaction>
However, I don't see why this would even be a commit problem, although
admittedly, I can't be sure what's going on in that stored procedure. I'm
guessing that it's just selecting data, right? If so, why would that be a
commit problem?
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
______________________________________________________________________
Get the mailserver that powers this list at http://www.coolfusion.com
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
