Re: "STATUS=HELD LOCK TYPE=READ" after SQL UPDATE

[Charles Wilt <charles.wilt@xxxxxxxxx>]

1) One system has a PTF the other doesn't
2) You're not running the same program.

For #2, how is the program being moved between systems?  SAVRSTOBJ, or did
you copy the source and compile it on each system separately,

If as I suspect the latter is the case, check to see that both programs
were created with the same options
CRTSQLRPGI  COMMIT(...) CLOSQLCSR(...)  in particular.

Might consider using SET OPTION in the program source to ensure they get
created the same.

Charles


On Tue, Jul 30, 2024 at 1:00 PM Reeve <rfritchman@xxxxxxxxx> wrote:

> After using *CHG commitment control at the job level, using a cursor "FOR
> UPDATE" to fetch and update a single record, and then using SQL COMMIT,
> DSPRCDLCK shows the record is in "STATUS=HELD LOCK TYPE=READ" status.
>
> The same very simple CRUD program running on another system (V7R5) in the
> same (I think) environment shows the record as being fully unlocked.  Both
> programs run in a named activation group and there's no funny stuff going
> on.
>
> The differing behaviors is what's getting me.  Why won't the system give me
> back my record?
>
> Thanks,
> Reeve
> --
> This is the RPG programming on IBM i (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/rpg400-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.