RE: Controlling values for Automatic STRCMTCTL

Dieter,
changing the commitment scope to job just ignores the activation group
boundaries, i.e. the transaction is not restricted to an activation group
but to the job.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser


"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
?Train people well enough so they can leave, treat them well enough so they
don't want to.? (Richard Branson)


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of D*B
Sent: Donnerstag, 15. April 2021 19:54
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Controlling values for Automatic STRCMTCTL

<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