Examples: Reclaim Object Links (RCLLNK) command
These examples describe situations in which the Reclaim Object Links (RCLLNK) command can be used to reclaim objects in the "root" (/), QOpenSys, and mounted user-defined file systems.
- Example: Correcting problems for an object
In this situation, the known problems are isolated to one object. The object is damaged and unusable, and you cannot restore a backup version of the object from media. You need to correct the problem quickly without disrupting normal file system operations.
- Example: Correcting problems that exist in a directory subtree
In this situation, the known problems are isolated to a group of objects within a directory subtree. An application is failing due to the problems within the directory subtree. You need to correct the problems quickly without disrupting normal file system operations.
- Example: Finding all damaged objects in the "root" (/), QOpenSys, and mounted user-defined file systems
In this situation, a disk failure has caused damage to a number of objects. You must identify the damaged objects before determining how to properly recover them.
- Example: Deleting all damaged objects in the "root" (/), QOpenSys, and mounted user-defined file systems
In this situation, a disk failure caused a number of objects to become damaged. You must delete the damaged objects so that a backup copy of the objects can be restored from media.
- Example: Running multiple RCLLNK commands to quickly reclaim all objects in the "root" (/), QOpenSys, and mounted user-defined file systems
In this situation, as part of routine system maintenance, all objects in the "root" (/), QOpenSys, and mounted user-defined file systems are reclaimed. You want to finish the reclaim operation as quickly as possible to allow for additional system maintenance to be completed.
Parent topic:
Reclaim operation of the "root" (/), QOpenSys, and user-defined file systems