× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. April 2021

Re: Controlling values for Automatic STRCMTCTL

<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

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.