sponsored links

Collapse

Announcement

Collapse
No announcement yet.

CPF5009 and CPF5026

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • CPF5009 and CPF5026

    Hello all,

    I have a RPG program that's working fine (more than 500 process per day), ecxept that 2/3 times a day I have the following error:

    Additional Message Information

    Message ID . . . . . . : CPF5009 Severity . . . . . . . : 10
    Message type . . . . . : Diagnostic
    Date sent . . . . . . : 13/07/20 Time sent . . . . . . : 13:30:33

    Message . . . . : Duplicate record key in member CBIQCPL0.
    Cause . . . . . : The output or update operation to member number 1 record
    number 0 format GIQCPJY, for member CBIQCPL0 file CBIQCPL0 in library FXGR,
    failed. Member number 1 record number 554 format GIQCPJY has the same record
    key as member number 1 record number 0 format GIQCPJY. 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.


    Message ID . . . . . . : CPF5026 Severity . . . . . . . : 30
    Message type . . . . . : Notify
    Date sent . . . . . . : 13/07/20 Time sent . . . . . . : 13:30:33

    Message . . . . : Duplicate key not allowed for member CBIQCPL0.
    Cause . . . . . : An output or update operation on member CBIQCPL0 failed
    because of a duplicate key in member CBIQCPL0 file CBIQCPL0 in library FXGR.
    Recovery . . . : See previously listed message CPF5009 to identify the
    record with the duplicate key. Then change the key value so that each key
    is unique and try your request again.
    Possible choices for replying to message . . . . . . . . . . . . . . . :
    C -- The request is canceled.
    I -- The request is ignored.


    I cannot determine the issue...

    Did you already faced this kind of issue ? Do you have any idea what could cause this issue and how to avoid it ?

    Thanks,

    Pierre.

  • #2
    It depends on what your program is doing. The message is obvious that it is trying to write a record where the unique key values match another record in the table. It tells you which existing record the new record matches. Look at the table to see what unique constraints are on it because there could be multiple and figure out which one is causing the duplicate error - sometimes it is not the obvious one. Look into what the program is doing that should prevent duplicates, if you can't figure that out then show us that part of the code.

    Comment

    Working...
    X