Re: SQL Lock Pro: Bruce Hoffman

[JReksodiputro@xxxxxxxxxx]

Hi Bruce,

Thanks a lot.
I know it must be something "simple-but-essential" that I missed.
The SQLRPGLE program is actually a module (it's bound to the CL driver program).

The compiler option for the SQLRPGLE, before:
*    COMMIT(*None)
*    Close SQL Cursor - CLOSQLCSR(*EndActGrp)

And, the program ActGrp is *CALLER

I didn't think that I should care about the CLOSSQLCSR before (just using the
default), because I was thinking it just used the "EXECUTE IMMEDIATE", but I
forget that it's a dynamic SQL that actually combines "PREPARE" and "EXECUTE",
and moreover it:
*    Specifies when SQL cursors are implicitly closed,
*    when SQL prepared statements are implicitly discarded,
*    and when LOCK TABLE locks are released.
(is this explanation accurate at all?)

So,
then I recompile the SQLRPGLE module with:
*    COMMIT(*None)
*    CLOSQLCSR(*EndMod)

And, all is working fine.

Thanks,

Jean Reksodiputro
Harrisburg, PA