Re: Find source of object lock?

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Pseudo-closed "cursors" are internal to the Db.

You get them anytime you read the Db.

They do not require an explicit DECLARE CURSOR.

Charles


On Tue, Feb 9, 2021 at 12:26 PM Justin Taylor <jtaylor.0ab@xxxxxxxxx> wrote:

> I don't know for sure when this first appeared, but I checked Subversion
> for any source changes that roughly correspond with the first known
> appearance.  I found these two SQL statements were added:
> EXEC SQL
>   insert into UNRELATED_TABLE
>     select *
>       from LOCKED_TABLE
>       where KEY like :hostVariable;
> EXEC SQL
>   delete from LOCKED_TABLE
>       where KEY like :hostVariable;
>
> I looked at that before but it doesn't declare a cursor, so I dismissed
> it.  Since I'm clearly missing something, I decided to look at it again.  I
> added QSYS2.JOB_LOCK_INFO queries before, between and after those two SQL
> statements, logging the results.  Next time the issue presents itself I'll
> compare the logs of the offending job and a non offending job.
> --
> 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.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com