Re: QOpenSys and the symbolic link issue -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

WRKSYSSTS should be smart enough to understand symlinks. It shouldn't be misreporting the disk space... If it is, I would report that as a bug to IBM, and they should fix it.

However, Windows tools are another matter. On IBM i or Unix systems, tools can easily tell whether a disk object is a symlink or an actual object. But, this is not true of Windows, which has no notion of symbolic links.

So... I wouldn't recommend using Windows tools for disk analysis on IBM i.

On 10/2/2012 1:31 PM, Matt Olson wrote:

I have been investigating the issue of QOpenSys issue as described here: http://www.itjungle.com/fhg/fhg062409-story03.html and the original article here: http://www.itjungle.com/fhg/fhg041509-story03.html and it appears to cause misreporting of the available free disk space when you run wrksyssts by precisely 15 times the amount of data in /QOpenSys due to the recursive symbolic link.

Has anyone else experienced this?

When running windows based tools against the IFS this also causes problems because it traverses every symbolic link upto the maximum depth (15) and you end up getting very inflated disk usage numbers. In our case 88GB of disk usage that isn't actually being used.

Matt

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.