Re: Controlling values for Automatic STRCMTCTL

The clue is in the note Dieter ... "but as they move into the wonderful world of ILE".

The current process that causes commitment control to start is issued from OPM (i.e. in the DAG) and _cannot_ be moved from there. It is just not possible due to the structure of the application.

*JOB is not an issue in their context because these are (relatively) short running batch jobs.


Jon

On Apr 15, 2021, at 3:04 AM, D*B <dieter.bender@xxxxxxxxxxxx> wrote:

<jon>
I have a customer situation where commitment control is being automatically started by the simple expedient of issuing an SQL COMMIT.

The problem is that the system uses a default of *ACTGRP for the scope when it is sorted like this. Up until now that has not mattered, but as they move into the wonderful world of ILE, they need the scope to be *JOB.

It is impossible to move the current start point into ILE and it could be a massive amount of work to add the correct STRCMTCTL to each job stream.

So - the obvious answer would be to find a way to change the default scoping - but I can't see any way to do that, You can use SET OPTION to change a bunch of things but commitment scope does not appear to be one of them.

Has anyone encountered this requirement and know if it can be done?
</jon>

Normally I would try to avoid commitscope *Job and look for alternatives. What's the problem with commitscope Activation Group?

Dieter
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com