Ansicht
Dokumentation

CPD32CF - Distributed file error, reason code &6. ( OS/400 )

ROGBILLS - Synchronize billing plans   General Material Data  
This documentation is copyright by IBM.


Message : CPD32CF
Distributed file error, reason code &6.

Message Long Text :

Cause . . . . . : Distributed file &1 in library &2 can not be created, or the operation could not be completed because of an error. The field &3, is not valid for reason code &6. The reason codes and their meanings are as follows:
00 - See previous messages.
01 - Duplicate partition key field.
02 - Partition key field does not exist.
03 - Date, time, timestamp, binary floating-point, and DataLink fields are not allowed in the partition key.
04 - The file can have a maximum of one member.
05 - The file cannot be in the QTEMP library.
06 - The file cannot be a source file.
07 - The file must be an externally described file.
08 - Join files are not allowed.
09 - The maximum number of based on files must be 1.
10 - Node group for the file does not exist.
11 - FCFO access paths are not allowed.
12 - Unique access path not valid.
13 - RDB entry not found in RDB directory.
14 - Error creating query temporary result file.
15 - DB2 MultiSystem not installed.
16 - The file key, LANGID, or SRTSEQ must match the distributed file.
Recovery . . . : Do one of the following based on the reason code shown, and then try the request again.
01 - Remove the duplicate partition key field.
02 - Change the partition key field to a valid field.
03 - Remove the date, time, timestamp, binary floating-point, or datalink field.
04 - Change the file to maximum members of one.
05 - Use a library other than the QTEMP library.
06 - Use a file other than a source file.
07 - Use an externally described file.
08 - Do not use the join file.
09 - Use only 1 based on file.
10 - Create the node group for the file.
11 - Remove the FCFO access path.
12 - Any distributed file with an unique access path, is required to have all the partition key fields as key fields for the unique access path.
13 - Make sure all RDB entries specified in original node group exist in the RDB directory by using the WRKRDBDIRE command.
14 - See previous messages received from the target system.
15 - DB2 MultiSystem must be installed.
16 - Delete and recreate the file so its key, LANGID, and SRTSEQ matches the distributed file.
Technical description . . . . . . . . : &3

Message File : QCPFMSG
Library Message File : QSYS2924


TXBHW - Original Tax Base Amount in Local Currency   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by IBM.

Length: 3289 Date: 20240509 Time: 004429     sap01-206 ( 3 ms )