× 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.


  1.  Home
  2. MIDRANGE-L
  3. April 2011

Re: Mistake running ADDLNK OBJ('/qsys.lib') NEWLNK('/test/')

The WRKLNK command you need is:

WRKLNK DETAIL(*EXTENDED) DSPOPT(*ALL)

That way you will see all the symlnk: like:

Opt Object link Type
. DIR
.. DIR
bin SYMLNK->DIR
core STMF
dev DIR
etc DIR

The *all will show you hidden files as well...

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 4/13/2011 3:54 PM, Joe Pluta wrote:
You might want to double check for your own peace of mind - do a wrklnk
and then look at the attributes for /nate. You should see SYMLNK right
at the top. The only reason I didn't worry about it is that I don't
think you can even make a hard link from the IFS to a QSYS library.

Joe

> All objects in the QSYS library are also listed in the/test/ directory. Now how
> can I get rid of the/test/ directory without deleting objects in the QSYS
> library?
>
> I think I made a mistake in playing with the ADDLNK command.
>
> -Nathan
>

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.