Re: Attempt to write duplicate record... -- RPG400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

On 15-Nov-2011 08:29 , Robert Rogerson wrote:

I had a stored procedure fail with RNX1021 Attempt to write a
duplicate record to file SIGNTMP.

<<SNIP>> I thought this was pretty solid code but the program still
failed. A new record is only written if a record with the same key
is not found.

Apparently not so solid ;-) at least with regard to the potential for concurrency.

So my only explanation is that another process wrote a record with
the same key in between the Chain and the Write.

Presumably.

Am I missing something of does some have another explanation.

There are other possibilities that can arise due to nuances in how the validation was accomplished and\or data inserted. But ssuming the most obvious, simple, and consistent means used to lookup and then insert the identical data as key, the most obvious origin from another thread\process having won the race to get the insert of the previously verified non-existent key.

<<SNIP>>

Seek the answer from the journal, comparing the timestamp the
RRN was added and that of the failed insert.

Regards, Chuck

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.