Ansicht
Dokumentation

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

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


Message : CPD32BA
Physical file constraint not valid.

Message Long Text :

Cause . . . . . : An add physical file constraint operation was not valid because of reason &3.
1 -- Field not in the format of the file.
2 -- Field not eligible to be constraint key.
3 -- Field not in the access path.
Recovery . . . :
1 -- Change field &4 and try the request again.
2 -- Change the request to be for a unique constraint so an access path that meets the key criteria can be found or one will be created. Key &4 in the key specification for file &1 in Library &2 has been specified with one of the following attributes, making it not valid for use as a field in a constraint: Descending order, use of alternative collating sequence, absolute value, zone, digit, or unsigned numeric.
3 -- Do one of the following:
-- If field &4 is not in the access path, correct the field name.
-- If field &4 is in the wrong order for the access path, reorder the field names to match the access path fields.

Message File : QCPFMSG
Library Message File : QSYS2924


BAL Application Log Documentation   ROGBILLS - Synchronize billing plans  
This documentation is copyright by IBM.

Length: 3233 Date: 20240423 Time: 230123     sap01-206 ( 2 ms )