Ansicht
Dokumentation

CPF5CA9 - Change record number &1 is invalid. ( OS/400 )

ABAP Short Reference   ABAP Short Reference  
This documentation is copyright by IBM.


Message : CPF5CA9
Change record number &1 is invalid.

Message Long Text :

Cause . . . . . : Object &3 type *&5 in library &4 was not changed. Change record number &1 contains an invalid value. The value specified was &6 &7 &8. The reason code is &2. The reason codes are:
-- 1: Invalid key value.
-- 2: Key value not valid for object type.
-- 3: Generic or *ALL specified when member name is being changed.
-- 4: Invalid data field value.
-- 5: Required data field value was not provided.
-- 6: Duplicate module names resulted from the change.
-- 7: Service Program &6 library &7 not found.
-- 8: Not authorized to service program &6 in library &7.
-- 9: Signature for service program &6 in library &7 does not match the signature for the current bound service program.
--10: Service program library name can not be changed when ALWLIBUPD(*NO) was specified during object creation.
--11: If blanks specified for one field, all must be blank.
--12: Export source file not found or not authorized.
Recovery . . . : The recovery is to make the required changes to the API input parameters and invoke the API again. See the API documentation for further information on the format of the change records. The specific recovery for each of the reason codes is as follows:
-- 1:Specify a supported key value.
-- 2:Specify a valid key value based on the object type of the object being changed.
-- 3:Specify a "From member" name other than *ALL or a generic name when changing the source file member name, or change the "To member" value to *SAME.
-- 4:Correct the indicated invalid input value.
-- 5:Supply the missing input value.
-- 6:Change the input values such that the requested change does not result in multiple bound modules with the same qualified object name.
-- 7:Specify the library name where the service program currently exists on the system.
-- 8:Obtain the required authority to the service program.
-- 9:Specify the library where the residing service program's signature matches the signature of the bound service program.
-- 10:Specify ALWLIBUPD(*YES) on the CRTSRVPGM command to allow the service program library name to be changed.
-- 11:Specify blanks for the source file library, file and member, or do not specify blanks for any of the fields.
-- 12:Specify an export source file that exists on the system and to which the API caller is authorized.

Message File : QCPFMSG
Library Message File : QSYS2924


BAL Application Log Documentation   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by IBM.

Length: 3265 Date: 20240425 Time: 170453     sap01-206 ( 3 ms )