|
On Apr 15, 2021, at 1:14 AM, Birgitta Hauser <Hauser@xxxxxxxxxxxxxxx> wrote:
Would changing the default in the STRCMTCTL command an option?
Otherwise, why not executing a STRCMTCTL at the job start with the
appropriated options?
Once Commitment control is started it can only be ended and restarted, but
not changed.
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 Jon
Paris
Sent: Donnerstag, 15. April 2021 01:12
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Controlling values for Automatic STRCMTCTL
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 Paris
--
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
--
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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.