Re: Commitment control problem

Darryl,

For all of those programs mentioned, you did not state what kinds of programs they are: CLP, CLLE, RPG, RPGLE, etc.,  or what activation group(s) they run in.

You could change DIR716 to run in its own named activation group, e.g. ACTGRP(DIR716), and that  should isolate it from the rest oft he job, since each activation group has its own "commitment control" scoping.

Hope that helps,

Mark S. Waterbury

> On 9/6/2017 10:50 AM, a4g atl wrote:

Who can help me with this problem? This may be a question for the RPG forum
but since its commitment control I am starting here.

- INC500 starts commitments control

- Calls INR500

- Calls INR501LRA ( this program does COMMIT or ROLLBACK)

- Calls INR664

- Calls INR651

o Updates D1P710 which fires a trigger calling D1R710T

After the COMMIT, I added a call to D1C716/D1R716. This program does not
need commitment control but the job has commitment control active

Problem:

1. The process is failing as one file D1L07302 is used once in INR651
in update and in D1R716 in read mode only.

2. D1C716 is called from various places which do not use commitment
control

4. When D1R716 executes, it gets a CPF error on D1L07302. Reading up
on the issue, the error message indicates that SHARE(*NO) is required. I
added a OVRDBF with SHARE(*NO) in D1C716 at CALLLVL. This did not resolve
the issue.

An option would be to submit the call to D1C716 to batch but if there is
an easier way in the same job, that would be the preferred solution.

TIA

Darryl Freinkel