Re: Data Area Issue

[RPower@xxxxxxxxxx]

Sorry. :(

Ron Power
Programmer
Information Services
City Of St. John's, NL
P.O. Box 908
St. John's, NL
A1C 5M2
Tel: 709-576-8132
Email: rpower@xxxxxxxxxx
Website: http://www.stjohns.ca/
___________________________________________________________________________
Success is going from failure to failure without a loss of enthusiasm. - 
Sir Winston Churchill




"James H H Lampert" <jamesl@xxxxxxxxxxx> 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
22/02/2005 02:25 PM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
<rpg400-l@xxxxxxxxxxxx>
cc

Subject
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


-- 
This is the RPG programming on the AS400 / 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.