CPF4326 in RPGLE program called by SQLRPGLE program -- Gina Whitney or Barbara Morris you out there?

A commitment definition can be explicitly started through the Start
Commitment Control (STRCMTCTL) command. If not already started, a
commitment definition is implicitly started when the first SQL statement is
executed under an isolation level different than COMMIT(*NONE). More than
one activation group can share a job commitment definition.

That was copied out of the SQL Reference. The SQL Programming "book" in
the infocenter also has information about commitment control.

date: Mon, 2 Feb 2009 11:17:46 -0500
from: Charles Wilt <charles.wilt@xxxxxxxxx>

All,

I'm restarting this thread for those you might have missed it late
Friday. Also, I'm hoping somebody with more expertise, ie. Gina or
Barbara :), will provide confirmation that this is working as designed
or that I should open a PMR.

I've got an SQLRPGLE program that calls an RPGLE program, the RPGLE
program is getting a CPF4326 - Commitment definition *N not valid for
open of FCONTRL0 when trying to open a file under commitment control.

Cause . . . . . : Commitment definition *N is not valid for open of

member

FCONTRL0 file FCONTRL0 in library HLTHITGDTA for one of the following

reasons:

-- Member FCONTRL0 was opened for commitment control when
commitment definition *N was not active.
-- Uncommitted changes are pending for member FCONTRL0 for a
commitment definition other than *N.
-- The calling program is using commitment definition *N which has
a scope of *ACTGRP, while the program specified to open the file using
a scope of *JOB.

The SQLRPGLE program specifies COMMIT(*CHG), DFTACTGRP(*NO) ACTGRP(*NEW)

The RPGLE program specifies DFTACTGRP(*NO) ACTGRP(*CALLER)


As it turns out, the cause of the CPF4326 was reason 1 - commitment
definition not active.

**SPECIFICALLY**

The SQLRPGLE program may or may not execute a set of SQL statements
(using commitment control) before calling the RPGLE program.

If the SQLRPGLE runs the SQL statements, and calls RPGPGMA, the process

works.

If the SQLRPGLE doesn't run any SQL statements, and just calls the
same RPGPGMA, the process fails with the CPF4326.

It appears that the SQLRPGLE program doesn't actually start commitment
control until the first SQL statement needing commitment control is
run.

Is this working as designed?

Thanks!
Charles Wilt