Re: IFS symbolic links

[Scott Klement <klemscot@xxxxxxxxxxxx>]

STRQSH CMD('ls -l /')

It will show an 'l' in the first position of the listing to indicate a
link, and at the end, you'll see the link, followed by a ->, followed
by the file it's linked to.

In your example, it would like:

lrwxrwxrwx  1 QSYS     0                    hom -> /home


On Wed, 18 Dec 2002, Peter Dow wrote:

> Hi Everyone,
>
> Ran into an interesting problem today.  I have a client at V4R4M0 who was
> having exceedingly long response times using Windows Explorer to drag a file
> into a directory in the IFS (e.g. from C:\temp\somefile.csv to
> \\AS400\home\xyz).
>
> When I tried
>     CD '/'
>     WRKLNK
>
> the first display came up immediately; I pressed PgDn and it took 3 minutes
> and 28 seconds to get to the next display.  What I saw on that 2nd display
> was a symbolic link called "JDrive", which had apparently been linked at one
> time to a directory on an NT server, and the server had been renamed.
> Deleting the link solved the problem.
>
> My question is, after a symbolic link has been created (with ADDLNK), how
> can you find out what it was linked to?  To make this perfectly clear, try
> the following:
>
> ADDLNK OBJ('/home') NEWLNK('/hom')
> WRKLNK '/'
>
> Option 5 (display) on /hom simply shows the contents of /home.
> Option 8 (display attributes) does not show that /hom is a link to /home, it
> just shows that it's a link, when it was created, etc.
>
> Is there an API that shows that /hom is a link to /home?
>