We are using CF 5.0 to call stored procedures in mainframe DB2.
Here is the code:
<cftransaction>
<cfstoredproc datasource="#datasource#"
procedure="#listingDataSource#">
<cfprocparam type="IN"
cfsqltype="CF_SQL_VARCHAR"
value="#listingQueryString#"
dbvarname="@PARM-RZSTR-INPUT">
<CFPROCPARAM TYPE="OUT"
cfsqltype="CF_SQL_VARCHAR"
VARIABLE="code"
DBVARNAME="@PARM-RETURN-CODE">
<CFPROCPARAM TYPE="OUT"
cfsqltype="CF_SQL_VARCHAR"
VARIABLE="message"
DBVARNAME="@PARM-RETURN-MSG">
<CFPROCRESULT NAME = "RS1">
<CFPROCRESULT NAME = "RS2" resultset="2">
</cfstoredproc>
</cftransaction>
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?
Thanks!
George
[EMAIL PROTECTED]
______________________________________________________________________
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
