Ansicht
Dokumentation

CPDA0B7 - Unable to delete object due to reason &4. Object is &1. ( OS/400 )

ABAP Short Reference   BAL Application Log Documentation  
This documentation is copyright by IBM.


Message : CPDA0B7
Unable to delete object due to reason &4. Object is &1.

Message Long Text :

Cause . . . . . : Object &1 of type &2 with file ID &3 could not be deleted. The reason code is &4, and the error number is &5. Unless otherwise noted, the delete of the user-defined file system (UDFS) ended.
Reason codes are:
1-- Object is read only.
2-- Object in use.
3-- Not authorized to object.
4-- Operation not permitted on object.
5-- Directory contains objects.
6-- General error.
If *N or zero appears, information is not available or does not apply.
If the object's path name begins with '...', then some of the path name prefix is not displayed because the full path name is too long. Use the Qp0lGetPathFromFileID() API with object file ID &3 to get the full path name.
Recovery . . . : Perform the recovery for reason code &4 as follows and then retry. The recovery may require the UDFS to be mounted via the Add Mounted FS (MOUNT) command.
1-- Change the object's read only attribute, using the Change Attributes (CHGATR) command or Set Attributes (Qp0lSetAttr) API.
2-- If the object is checked out, use the Check In Object (CHKIN) command to check in the object. If the object is not checked out, allow time for the current operation to complete and then retry the command.
To determine what is currently using the object, you can use the Retrieve Object References (QP0LROR) API, or examine object's properties using System i Navigator.
3 & 4-- Contact your security officer, the object owner, or other authorized person to obtain the correct authority or appropriate privileges to use the object or the directories in the object's path.
The System i Security Reference, SC41-5302, contains authority information for the command.
5-- Directory contains one or more objects that cannot be deleted. See the previous messages in the job log, and perform the recovery for those messages.
6-- Retry the command. If this problem continues, contact your IBM service representative.
Technical description . . . . . . . . : If the error number is not zero, then use one of the following to determine the meaning of the error number.
- Use DSPMSGD CPExxxx, where xxxx is the error number, to display an error message containing more information about this error number.
- Display the following file that contains descriptions of error numbers: QSYSINC/H, member ERRNO.
Internal step number &6.

Message File : QCPFMSG
Library Message File : QSYS2924


ROGBILLS - Synchronize billing plans   PERFORM Short Reference  
This documentation is copyright by IBM.

Length: 3278 Date: 20240427 Time: 060305     sap01-206 ( 4 ms )