Re: IFS symbolic links

[dennis.e.lovelady@xxxxxxxxxxxxx]

if you use qshell, the ls -l command from there will show you the link.
>From CmdEntry, I'm not certain that there's a direct way.

HTH


Dennis E. Lovelady





"Peter Dow" <maillist@dowsoftware.com>
Sent by: midrange-l-admin@midrange.com
12/18/2002 05:30 PM
Please respond to midrange-l


        To:     <MIDRANGE-L@midrange.com>
        cc:
        Subject:        IFS symbolic links

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?