Re: Program user profile, adopted authority, and named activation groups

[Mark Waterbury <mark.s.waterbury@xxxxxxxxxxxxx>]

David,

An application developer (ISV package or custom in-house application) is responsible  establish commitment control for a job, either by issuing a STRCMTCTL command in some "appropriate place", usually some initial program of an application, and be sure to specify *CMTSCOPE(*JOB), unless you know for certain that the entire application will run in some (named) activation group, in which case you can issue STRCMTCTL with CMTSCOPE(*ACTGRP).

But if using activation group level commitment scope, you really need to be sure that there is no way the user can somehow invoke other programs that may run in a different activation group or the default activation group.

If the entire application is all ILE, and all programs run in ILE activation groups, and if they all use SQL, you might be able to rely on Db2i SQL to automatically create any needed commitment control scoping -- that is to say the Db2 SQL runtime will issue a STRCMTCTL "under the covers" if one is not already active for the job.


Hope that helps,

Mark S. Waterbury

> On Friday, November 14, 2025 at 01:07:46 PM EST, David Gibbs via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote: 





On Fri, Nov 14, 2025 at 11:59 AM David Gibbs <david@xxxxxxxxxxxx> wrote:

> Can anyone point me to a good explanation of a job's 'Commitment
> Definition'?  I've never used that before.
Also, where is a commitment defintion established for a job?

Is it associated with the program?  Job description?

Thanks!

davidf