Re: Release *SHRRD lock from SQL

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Bring your coding into the 21st century?

You really can't code like everybody goes home at 5pm anymore.

What is the specific reason this is a problem for you?
Trying to a CLRPFM?  Use an SQL DELETE.
Trying to do a RGZPFM?  Use a RGZPFM ALWCANCEL(*YES) to re-org while active.

Additionally, you might make sure that the WAITFILE() setting on the file
is something besides *IMMED.  That will give the system time to hard close
any pseudo-closed curosrs when you are trying to do something that needs
them to be closed.  Also check the DFTWAIT() of your job.


Or you can use
ALCOBJ CONFLICT(*RQSRLS)

to request that the lock caused by a pseudo-closed cursor be released.

Pseudo-Close cursor FAQ
https://www-304.ibm.com/support/entdocview.wss?uid=nas8N1017851

Charles



On Fri, Mar 10, 2017 at 7:57 AM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

> I have an internal procedure that reads a table using a SQL cursor.  I
> explicitly close the cursor before returning, but it seems to be keeping a
> *SHRRD lock on the PF.  What's the best way to eliminate this problem?
>
> TIA
> --
> This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
> mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: http://amzn.to/2dEadiD