Re: IFS symbolic links

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Peter

Use WRKLNK DETAIL(*EXTENDED) - then you get an option 12 that will show you
what entries are symbolic links, and what they point to.

E.g.

                            Work with Object Links

Directory  . . . . :   /home/VERN

Type options, press Enter.
  2=Edit   3=Copy   4=Remove   5=Display   7=Rename   8=Display attributes
  11=Change current directory ...

Opt   Object link            Type             Attribute    Text
__    .                      DIR
__    ..                     DIR
__    drwtsn32.log           STMF
__    nextlevel              DIR
__    overlay.ovl            STMF
__    q5733lst.savf          STMF
__    testxxx                SYMLNK->PGM
__    xcaspi.txt             STMF
__    CheckConstraints.t >   STMF
                                                                       Mor
If you put 12=Work with links against testxxx you get

                            Display Symbolic Link

Object link  . . . . . :   /home/VERN/testxxx



Content of Link  . . . :   /qsys.lib/vern.lib/testxxx.pgm

Press enter to continue.

F3=Exit   F5=Refresh   F12=Cancel   F14=Work with link content
F22=Display entire field

Note the F14=Work with link content, which takes you to the actual object
pointed at.

This stuff is really hidden, isn't it?

HTH

Vern

At 02:30 PM 12/18/2002 -0800, you 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?
>
> tia,
> Peter Dow