Re: [EXTERNAL] Commitment Control Issue

[Charles Wilt <charles.wilt@xxxxxxxxx>]

with commitment control, the record remains locked until commit.

Charles

On Thu, May 16, 2019 at 2:59 PM Alan Shore via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

> Hi Brian
> Am I missing something here
> I thought that once the record was updated, it is no longer locked
> If that is true - then your second scenario should not be a problem
>
> Alan Shore
> E-mail : ASHORE@xxxxxxxx
> Phone [O] : (631) 200-5019
> Phone [C] : (631) 880-8640
> 'If you're going through hell, keep going.'
> Winston Churchill
>
> -----Original Message-----
> From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf
> Of Brian Garland via MIDRANGE-L
> Sent: Thursday, May 16, 2019 4:56 PM
> To: midrange-l@xxxxxxxxxxxxxxxxxx
> Cc: Brian Garland <Brian.Garland@xxxxxxxxxx>
> Subject: [EXTERNAL] Commitment Control Issue
>
> I've run into a problem with record locks due to commitment control.
>
> If I update the same record in file A twice (via a service program call)
> in the same module/program it works fine even though the record is locked.
>
> If I update the record in file A via that same service program call and
> then update file B and file B has a trigger that updates file A it fails in
> the trigger program because of the record lock.
>
> This is with STRCMTCTL and both *ACTGRP and *JOB.  The trigger program is
> *CALLER and shows with the same activation group as the service program
> that does the file updates.
>
> Is there anything I can do to let the trigger update the locked record?
> It seems like there must be some way to do it if I can update the record
> twice in the first place.
>
>
> --
> Brian J. Garland
> Vermont Information Processing, Inc.
> brian.garland@xxxxxxxxxx
>
> --
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or company to whom they are addressed.
> Do not disclose, distribute, or copy this email to others outside your
> company. If you have received this email in error, please notify the sender
> immediately and delete this email from your system.
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
> unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives at
> https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com