RE: RPG Data Area *LOCK

["Dennis Lovelady" <iseries@xxxxxxxxxxxx>]

I thought Barbara had answered this exact question with this exact wording
(or close enough) here:
    http://archive.midrange.com/midrange-l/200309/msg00154.html

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
Money is better than poverty, if only for financial reasons. 


> We have jobs that run all day long - sleep 5 minutes, wake up looking
> for something to process, go back to sleep...
> In an effort to prevent our newly-mandated 'save while active' strategy
> from causing file and data area lock conflicts with these jobs, I
> inserted an ALCOBJ *EXCLRD on the relevant file(s) and/or data area(s)
> in the CLLE program. If a lock fails, it branches around the RPG call
> and sleeps for another 5 minutes. With file locks, things worked as
> expected. But with the data areas, when the CL gets the lock the called
> RPG then fails saying it can't obtain the lock. When I do a WRKOBJLCK,
> I
> find the only object that has a lock is the very same CL program that
> called the RPG. (The RPG does a "*lock in".)
>
> How come the RPG isn't sharing the lock that its own CL caller obtained?
> Are data area locks handled differently? Thanks for any help.