Ansicht
Dokumentation

CPF5272 - Records not added to member &4. ( OS/400 )

CPF5272 - Records not added to member &4. ( OS/400 )

ABAP Short Reference   Vendor Master (General Section)  
This documentation is copyright by IBM.
SAP E-Book


Message : CPF5272
Records not added to member &4.

Message Long Text :

Cause . . . . . : The records were not added to member &4 file &2 in library &3, because the records require more storage than is available for the system, file, or owner of the file.
Recovery . . . : The storage limit has been exceeded for reason code &7. The reason codes are:
1 -- User profile storage limit has been exceeded. Ask the security officer to assign more storage to the user profile of the file owner (specify the MAXSTG parameter on the CHGUSRPRF command). Then try the request again.
2 -- System storage limit has been exceeded. Delete any objects that are not needed, or use the RCLSTG command. Then try the request again.
3 -- Object storage limit has been exceeded. Member &8 file &9 in library &10 has reached its maximum size. No new records can be added to the file. There is no recovery.
4 -- Object storage limit has been exceeded. An access path of member &8 file &9 in library &10 has reached its maximum size. No new entries can be added to the access path. If the access path size is *MAX4GB, change its size to *MAX1TB using the Change Logical File command (CHGLF), if the file is a logical file, or the Change Physical File command (CHGPF), if the file is a physical file, using the ACCPTHSIZ keyword. If the size of the access path is already *MAX1TB then there is no recovery.
5 -- Object storage limit has been exceeded. An access path of member &8 file &9 in library &10 has reached its maximum size. Because of its internal structure, an IPL must be performed before additional entries may be added to the access path.
6 -- Object storage limit has been exceeded. An access path of member &8 file &9 in library &10 has reached its maximum size. Because of its internal structure, the access path must be rebuilt before entries may be added. If the access path is not uniquely keyed, you can rebuild the access path by first using the Change Logical File command (CHGLF), if the file is a logical file, or the Change Physical File command (CHGPF), if the file is a physical file, using the MAINT keyword to change it to rebuild maintenance. Then using the change command again to change the access path back to immediate maintenance. If the access path is uniquely keyed, you can rebuild the access path by using the Remove Member command (RMVM) to delete the file's member, and then using the Add Physical File Member command (ADDPFM), or the Add Logical File Member command (ADDLFM), to create the member and the access path. If the member is a physical file member you may want to save the member's data (SAVOBJ) before removing the member from the file.
7 -- Reason code can not be determined because a Distributed Data Management (DDM) file is being used. See the job log on the target system to determine the cause of the failure.
8 -- Object storage limit has been exceeded. The save file &2 in library &3 has reached its maximum size. No new entries can be added to the save file. There is no recovery.

Message File : QCPFMSG
Library Message File : QSYS2924


Vendor Master (General Section)   General Material Data  
This documentation is copyright by IBM.

Length: 3229 Date: 20240328 Time: 194924     sap01-206 ( 2 ms )