Re: Creating SQL Stored Procedures and Trigger programswithout DB2Query Manager and SQL Development Kit...

On 22/09/2009, at 11:14 AM, Steven Harrison wrote:

I see someone mentioned that the CLI code is run by the system in a
separate job though. If that's the case would that mean in would run in
a different activation group, which as far as I know would make
commitment control impossible? I haven't really had time to look into
the nuts and bolts of the CLI API so I could be way of the mark here...

CLI only runs in a separate job if you set "server mode" otherwise it runs in the current job.

Even in server mode commitment control is OK. Given that all the SQL requests will run in the separate job the commit/rollback functions run there too. Your only issue would be trying to combine SQL and native I/O in the same commitment definition and that can probably be solved by not using server mode.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------