Comments on: questions related to commitment control in RPGLE http://itknowledgeexchange.techtarget.com/itanswers/questions-related-to-commitment-control-in-rpgle/ Wed, 19 Jun 2013 19:19:38 +0000 hourly 1 By: philpl1jb http://itknowledgeexchange.techtarget.com/itanswers/questions-related-to-commitment-control-in-rpgle/#comment-79262 philpl1jb Fri, 16 Jul 2010 01:19:15 +0000 #comment-79262 At the job level, then it’s not being affected by other jobs.
Your job is either
1. Starting Commitment control, calling PGRMB, which calls PGM2, which starts commitment control (and sees an error)
or
2. failing to endcmtctrl maybe because on an error and then is reaching a point where it attempts to start commitment control again.
Phil

]]> By: tomliotta http://itknowledgeexchange.techtarget.com/itanswers/questions-related-to-commitment-control-in-rpgle/#comment-79256 tomliotta Thu, 15 Jul 2010 21:51:15 +0000 #comment-79256 What is your OS version/release? What is your DB2 group PTF level?

Some system functions have SQL at their core. For example, the CPYTOIMPF/CPYFRMIMPF commands run SQL internally and may create commitment definitions.

If you are creating a commitment definition, your boundary possibly needs to be a little more limited in scope. PGMB should probably start its own activation group. And PGMA apparently should run in the *CALLER activation group. Then you might be able to STRCMTCTL CMTSCOPE( *ACTGRP ) and reduce the chance of conflict.

Tom

]]>