RE: CPF5009 - Duplicate record key in member

The statement that is getting the error is a WRITE statement. Again,
this file has REUSEDLT= *YES. I wonder that is why it is showing the
record number even thought it is a WRITE statement.




-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, January 24, 2008 12:40 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: CPF5009 - Duplicate record key in member

Glenn,
I thought the same thing also, until reading the second level help
again.
It says if the record number was zero then it occurred on a write.

Did an update try to change the key?

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Glenn Gundermann" <ggundermann@xxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
01/24/2008 12:56 PM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
"RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
cc

Subject
Re: CPF5009 - Duplicate record key in member






Hi Lim,

It looks like your program is writing the same key twice. If you do a
dump on the error message and compare the values with the 1st record
listed in the error message, you should be able to determine what it is
writing. Then take a look at the program and try to figure out why.

Glenn Gundermann
ggundermann@xxxxxx
(647) 272-3295

One of our production program is getting a CPF5009 error. This is a

RPG

program and the statement that is causing the error is a WRITE
statement. I'm not understanding why this CPF is showing a non zero
record number for a write operation. The file does have "REUSEDLT" of
*yes. Could this be the cause?

thanks



Additional Message Information



Message ID . . . . . . : CPF5009 Severity . . . . . . . :

10

Message type . . . . . : Diagnostic

Date sent . . . . . . : 01/24/08 Time sent . . . . . . :
09:53:49


Message . . . . : Duplicate record key in member ORDET.

Cause . . . . . : The output or update operation to member number 1
record
number 1377 format ORDETR, for member ORDET file ORDET in library
APLUS2FMC,
failed. Member number 1 record number 1376 format ORDETR has the

same

record
key as member number 1 record number 1377 format ORDETR. If the
record
number is zero, the duplicate record key occurred on an output
operation.
Recovery . . . : Change either record key so that the keys are
unique.
Then try your request again.