×
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.
Do the data types of your key list match the data types of the file keys?
Why not use SETLL instead of CHAIN?
That looks odd to push p_store into wkcus#.
Paul Morgan
-----Original Message-----
From: rpg400-l-bounces+paul.morgan=staples.com@xxxxxxxxxxxx [mailto:rpg400-l-bounces+paul.morgan=staples.com@xxxxxxxxxxxx] On Behalf Of Robert Rogerson
Sent: Tuesday, November 15, 2011 11:29 AM
To: RPG programming on the IBM i / System i
Subject: Attempt to write duplicate record...
Hi All,
I had a stored procedure fail with RNX1021 Attempt to write a duplicate
record to file SIGNTMP.
WKDOC#
Number of fields in key . . . . . . . :
4
In the code I have...
// Write to the work file if not already there
Chain(n) (p_store: p_item: p_DocumentType: p_Document) signtmp;
If not %Found(signtmp);
wkcus# = p_store;
wkitm# = p_item;
wkdoct = p_DocumentType;
wkdoc# = p_Document;
Write signtm;
Endif;
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.
So my only explanation is that another process wrote a record with the
same key in between the Chain and the Write.
Am I missing something of does some have another explanation.
BTW, I understand that I can add an error extender to the Write and
capture the error but my question still remains if there's another
explanation for the failure...
Thanks for all ideas,
Robert Rogerson
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: Attempt to write duplicate record..., (continued)
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
copyright@midrange.com.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.