Ansicht
Dokumentation

CPD32B0 - Constraint is not valid. ( OS/400 )

CL_GUI_FRONTEND_SERVICES - Frontend Services   ROGBILLS - Synchronize billing plans  
This documentation is copyright by IBM.


Message : CPD32B0
Constraint is not valid.

Message Long Text :

Cause . . . . . : Constraint &12 cannot be added for file &1 in library &2 for TYPE value &4. For a referential constraint (TYPE *REFCST), the parent file &5 in library &6 has a delete rule of &10 and update rule of &11. The constraint was not added because of errors. The reason code is &7. The reason codes and their meanings are as follows:
00 - See previous messages.
01 - Constraint name not valid.
02 - TYPE value not valid.
03 - DLTRULE value not valid.
04 - UPDRULE value not valid.
05 - File is damaged.
06 - File constraints are logically damaged.
07 - System Cross Reference files are damaged.
08 - A primary key constraint already exists.
09 - A duplicate unique constraint exists.
10 - The KEY length is too long.
11 - The parent file does not exist.
12 - The parent key does not exist.
13 - The file can have a maximum of one member.
14 - The file cannot be a source file.
15 - The file cannot be in the QTEMP library.
16 - The parent and dependent files must be in the same ASP.
17 - The file does not allow write, update, or delete operations
18 - The file must be an externally described file.
19 - The file must not be a distributed file.
20 - CHKCST not compatible with data type.
Recovery . . . : Do one of the following based on the reason code shown, and then try the request again.
01 - Correct the constraint name and retry the function.
02 - Correct the TYPE value and retry the function.
03 - Correct the DLTRULE value and retry the function.
04 - Correct the UPDRULE value and retry the function.
05 - Delete (DLTF) the file.
06 - Remove (RMVPFCST) the damaged constraints.
07 - Perform a reclaim storage (RCLSTG).
08 - Remove the primary key constraint (RMVPFCST) and then try again.
09 - Remove the unique constraint (RMVPFCST) and then try again.
10 - Choose fields whose combined length does not exceed the maximum
length allowed. See the Database User's Guide.
11 - Create (CRTPF) the parent file.
12 - Add primary key or unique constraint (ADDPFCST) to parent file.
13 - Change the file (CHGPF) to maximum members of one.
14 - Use a file other than a source file.
15 - Use a library other than the QTEMP library.
16 - Use files in the same ASP.
17 - Use a file that allows write, update and delete operations.
18 - Use an externally described file.
19 - Use a file which is not a distributed file.
20 - Use a data type compatible with the CHKCST.
Technical description . . . . . . . . : &3

Message File : QCPFMSG
Library Message File : QSYS2924


RFUMSV00 - Advance Return for Tax on Sales/Purchases   General Data in Customer Master  
This documentation is copyright by IBM.

Length: 3292 Date: 20240419 Time: 030952     sap01-206 ( 6 ms )