Re: Record Lock under Commitment Control

[Don Brown <DBrown@xxxxxxxxxx>]

You could NOT do chain-update-update on System 34.

Although the Baby/34 product that would run RPG code on a PC did allow 
this and finding that error took quite some time!!!!

Cheers

Don




From:   "x y" <xy6581@xxxxxxxxx>
To:     "Midrange Systems Technical Discussion" 
<midrange-l@xxxxxxxxxxxxxxxxxx>
Date:   25/02/2022 05:09 AM
Subject:        Re: Record Lock under Commitment Control
Sent by:        "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>



You could do a chain-update-update on primitive systems--that would be the
System/3, System/4, and System/36.  Those programs blew up on the 
System/38
and AS/400 (which is what it was called back then).

On Wed, Feb 23, 2022 at 9:57 AM Rob Berendt <rob@xxxxxxxxx> wrote:

> Interesting.
> It might be interpreted as I could do a
> Chain
> Update
> Update
> The first update may release the lock but it would still keep the 
pointer
> so the next update would also work.  As long as the second update is 
within
> the same commitment definition.
>
> But that's a guess.
>
> I wonder what this would show in between the updates
> https://www.ibm.com/docs/en/i/7.4?topic=services-record-lock-info-view
>
>
> Rob Berendt
> --
> IBM Certified System Administrator - IBM i 6.1
> Group Dekko
> Dept 1600
> Mail to:  7310 Innovation Blvd, Suite 104
>           Ft. Wayne, IN 46818
> Ship to:  7310 Innovation Blvd, Dock 9C
>           Ft. Wayne, IN 46818
> http://www.dekko.com
>
> -----Original Message-----
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
> Vinay Gavankar
> Sent: Wednesday, February 23, 2022 12:25 PM
> To: Midrange Systems Technical Discussion 
<midrange-l@xxxxxxxxxxxxxxxxxx>
> Subject: Re: Record Lock under Commitment Control
>
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
> So what does the below mean?
>
> I found this under IBMs Commit Lock Level documentation:
> Within the same job, a program can change a record that has already been
> changed within the current transaction as long as the record is accessed
> again using the same commitment definition. When using the job-level
> commitment definition, the access to the changed record can be made from 
a
> program running within any activation group that is using the job-level
> commitment definition.
>
> I can only update the record only in the same program? Doesn't it kind 
of
> defeat the purpose of 'transaction'?
>
> On Wed, Feb 23, 2022 at 12:14 PM Rob Berendt <rob@xxxxxxxxx> wrote:
>
> > There is no "other"  If it's locked, it's locked.
> > <snip>
> > even though it is kept locked for other jobs or programs
> > </snip>
> >
> > Rob Berendt
> > --
> > IBM Certified System Administrator - IBM i 6.1
> > Group Dekko
> > Dept 1600
> > Mail to:  7310 Innovation Blvd, Suite 104
> >           Ft. Wayne, IN 46818
> > Ship to:  7310 Innovation Blvd, Dock 9C
> >           Ft. Wayne, IN 46818
> > http://www.dekko.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@xxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com