Re: Hanging pending commits

[Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>]

Rob

I believe you can use ENDCMTCTL to clear these definitions - of course, 
be careful about anything you are actually doing yourself with 
commitment control.

Vern

On 9/20/2012 8:09 AM, rob@xxxxxxxxx wrote:
> I've been "enlightened".  Apparently there were no hanging commits, just a
> hanging commitment definition.
> When you do a DSPJOB OPTION(*CMTCTL) you may see something like this:
> Commitment
> Definition     Text
> *DFTACTGRP     Default activation group
> Q1ABRMS        Activation-group-level
>
> The first one was because I am using STRSQL with commitment control
> enabled.  The second is left over from BRMS.  If I display the STRSQL one
> I will see:
> Local pending changes . . . . . . :   YES
> Until I COMMIT then it changes to NO.
> While the BRMS one shows:
> Local pending changes . . . . . . :   NO
>
> Now I exit STRSQL.  I've been out of BRMS.  I still see in DSPJOB
> OPTION(*CMTCTL)
> Commitment
> Definition     Text
> *DFTACTGRP     Default activation group
> Q1ABRMS        Activation-group-level
> Until I signoff or reclaim these activation groups.  Since I haven't
> figured out how to reclaim the default activation group I can use a sign
> off.
>
> BRMS doesn't want to end their activation group in case you enter more
> BRMS commands.  Leaving it there helps performance.
>
> RCLSTG sees these commitment definitions and stops.  In which case you
> either sign off/on or reclaim these activation groups.
>
> I don't suppose there's a "clear commitment definitions that have no local
> pending changes" command, is there?
>
> Rob Berendt