RE: Constraint Violations

Rob wrote:
>Does it appear in the Program Status Data Structure in any of
>these related fields:
>.....DName+++++++++++ETDsFrom+++To/L+++IDc
>     D EXCP_MSG               40     46
> ¦   D EXCP_TYPE              40     42
> ¦   D EXCP_NUM               43     46
> ¦   D PGM_LIB                81     90
> ¦   D EXCP_DATA              91    170
> ¦   D LAST_FILE             201    208

Alas, no.  The first level text ends up in EXCP_DATA
EXCP_DATA
  CHAR(80)
  'Referential constraint violation on member PROMAS.

Here's the full message:
Message ID . . . . . . :   CPF502D       Severity . . . . . . . :   30



Message . . . . :   Referential constraint violation on member PROMAS.

Cause . . . . . :   The operation being performed on member PROMAS file
PROMAS
  in library BUCK failed. Constraint PROMAS_CUSTOMER_ID prevents record
number
  40 from being inserted or updated in member PROMAS of dependent file
PROMAS
  in library BUCK because a matching key value was not found in member
PROCUS
  of parent file PROCUS in library BUCK. If the record number is zero, then

  the error occurred on an insert operation. The constraint rule is 2. The

  constraint rules are:

    1 -- *RESTRICT

    2 -- *NOACTION


Program status is 00001
File status is 01022
  --buck