Is there ANY chance that the update/out logic failed and the data area did
not get incremented by the first process.
Paul
-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Roger
Harman
Sent: Friday, April 14, 2017 2:07 PM
To: 'RPG programming on the IBM i (AS/400 and iSeries)'
<rpg400-l@xxxxxxxxxxxx>
Subject: DTAARA Lock Issue?
We had two jobs submitted for the same process - different companies.
Each (RPGLE) does an IN *LOCK of a data area for a unique identifier.
Increment and then OUT for the next use.
From the joblogs, programs were initiated .06 seconds apart (6/100th's).
Both got the same unique ID. I can't see how this could happen. Default
wait time (job) should be 30 seconds, I believe.
There is no error indicator on the IN. If the LOCK failed and no indicator
specified, would the fail just be ignored?
Thanks.
Roger Harman
COMMON Certified Application Developer - ILE RPG on IBM i on Power
--
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
midrange.com
