Ansicht
Dokumentation

CPF3229 - File &1 not allowed as based-on file. ( OS/400 )

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


Message : CPF3229
File &1 not allowed as based-on file.

Message Long Text :

Cause . . . . . : The logical file or Structured Query Language (SQL) materialized query table (MQT) being created has file &1 in library &2 specified as a based-on file. However, file &1 in library &2 is not allowed as a based-on file for the file being created for one of the following reasons:
-- The logical file being created is not an SQL view, and the based-on file that is being used is not a physical file. All based-on files for logical files that are not views must be physical files.
-- The logical file being created is using a file that is not keyed as its access path definition file. The access path definition file must be keyed.
-- The logical file being created is being created into a permanent library, and the based-on file that is being used is not in a permanent library. If the logical file is being created into a permanent library, the based-on file must be in a permanent library.
-- An SQL MQT is being created, and the based-on file that is being used is not in a permanent library. Based-on files for an SQL MQT must reside in a permanent library.
-- The file being created is an SQL view or MQT, and the based-on file that is being used is a program-described physical file. Based-on files for SQL views and MQTs cannot be program-described physical files.
-- The file being created is an SQL view or MQT, and the based-on file that is being used is a logical file that is not a view file. Logical based-on files for SQL views and MQTs must be SQL views.
-- The logical file being created contains a concatenated field which is attempting to concatenate a field from the physical file which is null capable. Null capable fields cannot be concatenated together.
-- The logical file being created contains a concatenated field which is variable length and output capable. Variable length concatenated fields can not be output capable.
-- The logical file being created contains a concatenated field but the based-on physical file contains a field that allows the null value. Either make the concatenate field input only, remove the logical field that references the physical file based-on field that allows the null value or remove all occurrences of ALWNULL from the based-on physical file.
-- The logical file being created contains a concatenated field that is a binary character field, a UTF-8 character field or a UTF-16 graphic field which is also output capable. Binary character, UTF-8 character and UTF-16 graphic concatenated fields can not be output capable.
Recovery . . . : Change the based-on file name or the access path definition file name to a file that is permitted as a based-on file or as an access path definition file for the file being created. Then try the request again.

Message File : QCPFMSG
Library Message File : QSYS2924


rdisp/max_wprun_time - Maximum work process run time   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by IBM.

Length: 3239 Date: 20240426 Time: 084623     sap01-206 ( 2 ms )