Ansicht
Dokumentation

CPD32B9 - Physical file constraint not valid. ( OS/400 )

Addresses (Business Address Services)   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by IBM.


Message : CPD32B9
Physical file constraint not valid.

Message Long Text :

Cause . . . . . : An add physical file constraint operation was not valid because of reason &3.
1 -- The sort sequence tables are not compatible.
2 -- Field attributes do not match.
3 -- The CCSID is not compatible with the sort sequence table.
4 -- Arrival sequence file not allowed with *PRNFILE parameter.
5 -- An internal error occurred.
6 -- The field is a datalink, row change timestamp, or a LOB/XML field for a primary key, foreign key or unique constraint.
Recovery . . . :
1 -- Referential constraints between file &1 in library &2 and file &8 in library &9 cannot be added. The sort sequence tables must match before a referential constraint can be added.
2 -- The following attributes of field &4 and field &5 must match: data type, field length, if the fields are character or IGC fields the CCSIDs must match or one of the fields be CCSID 65535, if the fields are IGC fields, the keyboard shift must match, if the fields are zoned, packed or binary, the precision must match, if either field has a field procedure program, both of the fields must have the same field procedure program along with matching internal data attributes and parameter list entries. To correct the problem, do one of the following
-- Make sure the fields in the KEY and PRNKEY parameters are in the correct order so that the attributes of all the fields specified match.
-- Use a different field in that position.
3 -- The CCSID of field &4 is not compatible with the CCSID of the sort sequence table of file &1 in library &2. Change the field name, if possible, to a field that has a compatible CCSID or a CCSID of 65535.
4 -- Do one of the following:
-- First, add a primary key to file &1 in library &2 with the fields that you want to use. Then try this request again.
-- Change the PRNKEY parameter to specify the fields you want to use for the referential constraint.
5 -- Contact your IBM service representative. This reason code should not appear and indicates a problem with the internal system.
6 -- Do not use field &4 for the constraint.

Message File : QCPFMSG
Library Message File : QSYS2924


BAL_S_LOG - Application Log: Log header data   ROGBILLS - Synchronize billing plans  
This documentation is copyright by IBM.

Length: 3249 Date: 20240425 Time: 034335     sap01-206 ( 4 ms )