Re: Data area LOCK timeout

Thanks guys.

Yes, I'm seeing it on a client's box. It's something that I've used for
many many years without issue.

I am still waiting to hear if it's possible a backup or mirroring job could
have had a lock on the object instead of 2 jobs wrestling for the same
object.

Their default timeout is 30 seconds, so that shouldn't be the issue even if
100 jobs try to grab it at the same time.

Brad
www.bvstools.com

On Thu, May 26, 2016 at 12:44 PM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 5/26/2016 1:04 PM, Bradley Stone wrote:

I'm having a hard time finding an answer to this..

Let's say PGMA reads in data area DTAARA1 with *LOCK, updates the data

area

value , then uses OUT to update the data area (and unlock it).

PGMB also does the same thing. Let's say they happen to run at the same
time (but PGMA got there first)... how long does PGMB wait until it

issues

an error saying it can't lock the data area?

The update is very quick.. it's really just incrementing a counter value
stored in the data area and returning the value.

Are you seeing a hang? Getting a message?

Aside from DFTWAIT() I dimly recall an internal (system) lock when the
'write' actually occurs but I can't recall the error message that ensues
if it gets tripped.

--
--buck

Visit wiki.midrange.com and register for an account. Edit a page that
helps you, and because it's public, you'll help someone else, too!

--
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.