CPF502D: Referential constraint violation

What it means

A referential constraint links a dependent file to a parent file. An order line file, for example, can have a foreign key on the order number that points to the order header file. Once that constraint is in place, Db2 for i checks every insert and every change to the foreign key in the dependent file. The new value must match a key in the parent file.

CPF502D is the message the database sends when that check fails. Its first-level text says there was a referential constraint violation on the member. The second-level text, which you see with F1, names the constraint, the dependent file that was being changed and the parent file where no match was found. It is a notify message, so an application can handle it.

SQL reports the same failure as SQLCODE -530. Native record I/O gets CPF502D directly. ILE RPG sets file status 01022, and an RPG program with no error indicator, E extender or INFSR stops with inquiry message RNQ1022. ILE COBOL sets file status 9R.

A sibling message, CPF503A, has the same first-level text. Read the second-level text to see which rule and which direction failed.

Common causes

• A program added a dependent record before its parent existed, for example an order line for an order header that hasn't been written yet.
• A program changed the foreign key field to a value that isn't in the parent file, often a typing error or an old code that has since been removed.
• A data load or CPYF filled the dependent file before the parent file, or loaded only part of the parent data.
• The values look the same but don't match exactly, such as different leading zeros, case or trailing characters in a character key.
• Another job deleted the parent record a moment earlier.

How to find the problem

1. In the job log (DSPJOBLOG), put the cursor on CPF502D and press F1. The help names the constraint, the dependent file and member, and the parent file. Note the record and the key value the program was writing.
2. Show the constraint definition with DSPFD FILE(ORDLIB/ORDLINE) TYPE(*CST), or use WRKPFCST. The definition lists the foreign key fields and the parent key they must match. In SQL, QSYS2.SYSREFCST and QSYS2.SYSKEYCST hold the same details.
3. Look up the key in the parent file, for example with a SELECT against the parent table, to confirm it really is missing.
4. If an RPG program stopped with RNQ1022, the message before it in the job log is the CPF502D that explains why.

How to fix it

• Write the parent record first, then the dependent records. In a load, copy parent files before dependent files.
• Correct the foreign key value so it matches an existing parent key.
• If a missing parent is a normal business case, make the foreign key field null-capable and leave it null until a parent exists. A foreign key with a null value isn't checked against the parent.
• Handle the error in the program. Use an error indicator or the E extender and check for status 01022 in RPG, or file status 9R in COBOL, and send the user a clear message.
• For a large one-time load, an administrator can disable the constraint with CHGPFCST and enable it again afterwards. The database then checks the whole file and flags rows that don't match, so plan time to clean them up.

What it looks like

Referential constraint violation on member ORDLINE.

DSPMSGD MSGID(CPF502D) MSGF(QSYS/QCPFMSG)

Technical reviewer: Albert Joseph, WND Software.

Last reviewed 2026-10-18 by the WND Software team. Written in our own words. For the full reference, check IBM’s documentation for your IBM i release.