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

Sounds like timing then, to me. Forgot to sacrifice your first PC at the alter of the dead electronics, did we?

Way, way back I used to program IBM Series/1 systems, and the language (EDL) had a concept called Queue Control Block (QCB) that you could enqueue (lock) and dequeue (unlock) to prevent just this sort of thing. Those ENQ/DEQ commands were amazingly fast, even by today's standards. I often find myself wishing such a thing were available on this and other platforms. If we want the same sort of control, we have to lock some data area or some such.
++
Dennis
++
Never argue with a fool, because passers-by cannot tell you apart.

Sent from my Galaxy tablet phone. Please excuse my brevity.
For any grammatic/spelling errors, there is no excuse.
++

"Robert Rogerson" <rogersonra@xxxxxxxxx> wrote:

@Alan, @Dennis there are no logical built over this file.
DSPDBR Command Input
File . . . . . . . . . . . . . . . . . . . : FILE SIGNTMP
Library . . . . . . . . . . . . . . . . . : *LIBL
Member . . . . . . . . . . . . . . . . . . : MBR *NONE
Record format . . . . . . . . . . . . . . . : RCDFMT *NONE
Output . . . . . . . . . . . . . . . . . . : OUTPUT *
Specifications
Type of file . . . . . . . . . . . . . . . : Physical
File . . . . . . . . . . . . . . . . . . . : SIGNTMP
Library . . . . . . . . . . . . . . . . . : QS36F
Member . . . . . . . . . . . . . . . . . : *NONE
Record format . . . . . . . . . . . . . . : *NONE
Number of dependent files . . . . . . . . : 0

@Dennis, the job was running on a production machine and I didn't have
authority to view the joblog. I was able to view the RPG dump and see
the
values of the Chain/Write but I'm not sure this helps me.
From the code the Chain did not find a record but when it attempted a
Write (with the same values) the record now existed.

Thanks,

Robert Rogerson

On 2011-11-15 12:02 PM, Dennis wrote:

Correct. And the joblog will tell you which logical's rules were
violated, and (IIRC) give you the RRN of the matching record. (And I
thought I'd never say "matching record" in this century. Here I've
said it twice.)
++
Dennis
++
The cardiologist' s diet:
-- If it tastes good spit it out.

Sent from my Galaxy tablet phone. Please excuse my brevity.
For any grammatic/spelling errors, there is no excuse.
++

"Alan Shore" [1]<ashore@xxxxxxxx> wrote:

Hi Roger
Does the file have any logicals with unique keys
That can also create the problem that you are facing
Even though THIS file may not have a record already out there, data in
this write attempt may be a duplicate of that logical

Alan Shore
Programmer/Analyst, Direct Response
[2]E:AShore@xxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill

-----Original Message-----
From: [3]rpg400-l-bounces+ashore=nbty.com@xxxxxxxxxxxx
[[4]mailto:rpg400-l-bounces+ashore=nbty.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.

SIGNTMP has the following constraint:

Constraint
Description
Primary Key
Constraint
Constraint . . . . . . . . . . . . . . : CST
Q_QS36F_SIGNTMP_WK
Type . . . . . . . . . . . . . . . . : TYPE
*PRIMARY
Key . . . . . . . . . . . . . . . . . : KEY
WKCUS#

WKITM#

WKDOCT

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
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list To post a message email: [5]RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: [6]http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: [7]RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
[8]http://archive.midrange.com/rpg400-l.

--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list
To post a message email: [9]RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [10]http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: [11]RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [12]http://archive.midrange.com/rpg400-l.

References

Visible links
1. mailto:ashore@xxxxxxxx
2. mailto:E:AShore@xxxxxxxx
3. mailto:rpg400-l-bounces+ashore=nbty.com@xxxxxxxxxxxx
4. mailto:rpg400-l-bounces+ashore=nbty.com@xxxxxxxxxxxx
5. mailto:RPG400-L@xxxxxxxxxxxx
6. http://lists.midrange.com/mailman/listinfo/rpg400-l
7. mailto:RPG400-L-request@xxxxxxxxxxxx
8. http://archive.midrange.com/rpg400-l
9. mailto:RPG400-L@xxxxxxxxxxxx
10. http://lists.midrange.com/mailman/listinfo/rpg400-l
11. mailto:RPG400-L-request@xxxxxxxxxxxx
12. http://archive.midrange.com/rpg400-l
--
This is the RPG programming on the IBM i / System i (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.