Ansicht
Dokumentation

CPDA0B5 - Unable to correct problem &6 while reclaiming object &1. ( OS/400 )

RFUMSV00 - Advance Return for Tax on Sales/Purchases   General Material Data  
This documentation is copyright by IBM.


Message : CPDA0B5
Unable to correct problem &6 while reclaiming object &1.

Message Long Text :

Cause . . . . . : Problem &6 was found for object &1 of type &2 with file ID &7 that could not be corrected. The reason code is &3, and the error number is &4. The reclaim continued.
Problem codes are:
1-- Directory has a read error.
2-- Object is orphaned from its owning user profile.
3-- Object is damaged and usable.
4-- Object has an internal error.
5-- Missing system object.
6-- Object link refers to a deleted object.
7-- Object is damaged and unusable.
Reason codes are:
100-- Object in use.
101-- Object contains recoverable data.
102-- Object could not be created.
103-- DataLink File Manager (DLFM) server not started.
104-- General error.
105-- Object is a file system root directory.
106-- Parent directory object is damaged.
107-- Object could not be deleted.
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 &7 to get the full path name.
Recovery . . . : Perform the recovery for reason code &3 as follows. If the recovery fails, use the RCLSTG SELECT(*DIR) command.
100: The object may be in use. Refer to previously listed messages in the job log for more information. If the object is in use, allow time for the current operation to complete and then retry.
101: For a *STMF with problem codes 3 or 4, restore a copy from media, or delete the object after its data has been copied to a new *STMF.
For a *DIR with problem codes 1, 3, or 4, delete the *DIR after its contents has been moved to another *DIR.
For problem code 2, use the Change Owner (CHGOWN) command to change the object's owner.
If the recovery fails for problem codes 1 or 3, retry the command with the DMGOBJOPT(*DELETE *DELETE) option.
102: IPL to recreate the object.
103: Start the DLFM server using the STRTCPSVR SERVER(*DLFM) command and then retry.
104: Retry the command.
105: Use the RCLSTG SELECT(*DIR) command.
106: Use the Move Object (MOVE) command to move the object to a parent directory that is not damaged, and then retry.
107: Retry the command with the DMGOBJOPT(*DELETE *DELETE) option.
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 &5.

Message File : QCPFMSG
Library Message File : QSYS2924


SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Vendor Master (General Section)  
This documentation is copyright by IBM.

Length: 3306 Date: 20240508 Time: 044423     sap01-206 ( 2 ms )