System i: Reclaim Object Links (RCLLNK) and Reclaim Storage (RCLSTG) commands comparison

Reclaim Object Links (RCLLNK) and Reclaim Storage (RCLSTG) commands comparison

You can use both the Reclaim Object Links (RCLLNK) and Reclaim Storage (RCLSTG) commands to correct problems in the "root" (/), QOpenSys, and user-defined file systems.
The RCLLNK command identifies and, if possible, corrects problems in mounted file systems that are in use. The RCLSTG command does not have this function. However, the RCLSTG command can correct problems that the RCLLNK command is unable to identify or correct. The following table provides a more detailed comparison between the two commands.
Table 1. RCLLNK and RCLSTG command comparison
RCLLNK OBJ('/MyDir/MyObj')
RCLSTG ASPDEV(*SYSBAS)
RCLSTG ASPDEV(<IASPNAME>)
Is the system required to be in a restricted state? No Yes No
Are all file systems usable during the reclaim operation? Yes No The file systems in the independent ASP being reclaimed are unusable.
In what ASPs can objects be reclaimed? Reclaims objects in system, user, and independent ASPs. Reclaims objects in system and user ASPs. Reclaims objects in independent ASPs.
How are objects reclaimed? Objects are reclaimed on an individual or subtree basis as specified on the command. Objects are reclaimed on a system-wide basis. Objects are reclaimed on an independent ASP basis.
What known and applicable file system problems are identified and corrected, if possible? Most (See Reclaim operation of the "root" (/), QOpenSys, and user-defined file systems for more information.) All All
Are lost objects found? No Yes Yes
Are objects in unmounted file systems reclaimed? No Yes Yes
Is the command threadsafe? Yes No No
How many instances of the command can be performed at the same time? Multiple instances Single instance Single instance
What applicable integrated file system provided objects are re-created if necessary? All Most (See Re-creation of integrated file system provided objects for more information.) None
Can damaged objects be identified without being reclaimed? Yes No No
Parent topic:
Reclaim operation of the "root" (/), QOpenSys, and user-defined file systems

Related concepts

Examples: Reclaim Object Links (RCLLNK) command

Related reference

Re-creation of integrated file system provided objects

Related information

Reclaim Storage (RCLSTG) command
Reclaim Object Links (RCLLNK) command

	RCLLNK OBJ('/MyDir/MyObj')	RCLSTG ASPDEV(*SYSBAS)	RCLSTG ASPDEV(<IASPNAME>)
Is the system required to be in a restricted state?	No	Yes	No
Are all file systems usable during the reclaim operation?	Yes	No	The file systems in the independent ASP being reclaimed are unusable.
In what ASPs can objects be reclaimed?	Reclaims objects in system, user, and independent ASPs.	Reclaims objects in system and user ASPs.	Reclaims objects in independent ASPs.
How are objects reclaimed?	Objects are reclaimed on an individual or subtree basis as specified on the command.	Objects are reclaimed on a system-wide basis.	Objects are reclaimed on an independent ASP basis.
What known and applicable file system problems are identified and corrected, if possible?	Most (See Reclaim operation of the "root" (/), QOpenSys, and user-defined file systems for more information.)	All	All
Are lost objects found?	No	Yes	Yes
Are objects in unmounted file systems reclaimed?	No	Yes	Yes
Is the command threadsafe?	Yes	No	No
How many instances of the command can be performed at the same time?	Multiple instances	Single instance	Single instance
What applicable integrated file system provided objects are re-created if necessary?	All	Most (See Re-creation of integrated file system provided objects for more information.)	None
Can damaged objects be identified without being reclaimed?	Yes	No	No