Re: Data Area Issue

> I've searched the archives, but can't quite find an answer to my
> question  that I'm looking for.  I have the following piece of code:
>      ?* set receipt number
>      c     *lock         in        rec#dta
>      c                   eval      rec#dta = rec#dta + 1
>      c                   eval      precpt# = rec#dta
>      c                   out       rec#dta
> There can be mulitple versions of this program at any given time (cash
> receipts) and it seems that if both programs hit this the exact same
> time,  one blows up.  My questions are:
> 1. On the OUT opcode, does it automatically release the locks?  Or
> should  I be using the UNLOCK opcode as well?
> 2. Can I use lock logic here like record lock logic that RPG has?

First, RTFM! In the section on "IN," there's a paragraph about using
either the "E" extender or an error indicator to catch the exceptions that
are blowing you up, and in the Program Status Codes section, it lists 431
and 432 as lock conflicts. And in the section on "OUT," there's a
paragraph about using "*LOCK" to maintain the lock after the OUT
operation.

I hope this helps.

Just use the exception trap to keep the code from blowing up, then arrange
somehow to wait for the lock to be released.

--
JHHL