Ansicht
Dokumentation

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

Addresses (Business Address Services)   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by IBM.


Message : CPD32B4
Physical file constraint not valid.

Message Long Text :

Cause . . . . . : An add physical file constraint operation was not valid because of reason &3.
1 -- Field name specified twice.
2 -- Access path already primary key or unique constraint.
3 -- Access path is not unique.
4 -- The number of key fields does not match.
Recovery . . . :
1 -- Duplicate field names are not allowed in the key fields. Field &4 in file &1 in library &2 appears twice. Check the fields entered and remove the duplicate entry, then try the request again.
2 -- The access path for file &1 in library &2 is already a primary key or being used as a unique constraint. Do one of the following:
-- Remove the current primary key or unique constraint using the RMVPFCST CL command, then try the request again.
-- There is no need to try this function again as the desired primary key exists.
3 -- The access path for file &1 in library &2 has to be unique. Do one of the following:
-- If the request is for a primary key, make the request for a unique constraint. Then, either an existing access path will be used or a new access path will be created.
-- If the request is for a referential constraint and the parent file access path has been requested for the parent key (PRNKEY(*PRNFILE)), change the request to give the field names of the parent key.
4 -- There were &6 fields passed in for file &1 in Library &2. Either the file access path or the fields passed in for file &8 in library &9 has &7 fields. Do one of the following:
-- If there are more fields in the access path of the file than the fields requested, add the names of the additional fields to the request, then try the request again.
-- If there are more fields in the fields requested than the fields in the access path, remove the extra fields from the request list, then try the request again.
-- If the request is for a referential constraint, make sure the number of keys given on the KEY parameter is the same as the number of keys given on the PRNKEY parameter.

Message File : QCPFMSG
Library Message File : QSYS2924


Addresses (Business Address Services)   General Material Data  
This documentation is copyright by IBM.

Length: 3247 Date: 20240427 Time: 052247     sap01-206 ( 2 ms )