Re: Controlling values for Automatic STRCMTCTL

No - Dieter - the exact opposite.

Right now the commit starts in the DAG and that cannot (easily) be changed. As a result it is not in effect for any ILE programs introduced later in the call sequence. Right now they limit their ILE programs to running *CALLER which puts them in the DAG which is not a good environment to introduce Service Programs into.

Change the scope to *JOB and they can have the ILE programs run in QILE (or wherever) and SPs will be fine. *JOB scope in this context is not an issue as they are (relatively) short duration batch jobs.

I would approach the problem very differently under other circumstances but the client is stuck with what they have and are just looking for the safest options for moving forward.

By the way - I don't understand your comment "... changing this to *job, would limit commit to OPM possibilities ... " because that is _exactly_ what the current setting is imposing on them.


Jon

On Apr 15, 2021, at 1:53 PM, D*B <dieter.bender@xxxxxxxxxxxx> wrote:

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

... so the commitscope would be *dftactgrp: so what, where is the problem?
changing this to *job, would limit commit to OPM possibilities and preventing ile enhancements. I would not recommend, to do so!!!

D*B
--
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