RE: Finding members

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

--
[ Picked text/plain from multipart/alternative ]
Right, Eric. And you can "cd" to a physical file like

    cd '/qsys.lib/vern.lib/qcsrc.file'

Then WRKLNK looks "veeerrrrry interrrresting" (thank you, Arte Johnson)
(copy these lines into a text editor to see the formatting)

                             Work with Object Links

Directory  . . . . :   /QSYS.LIB/VERN.LIB/QCSRC.FILE

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
__    .                      FILE     PF           C source file
__    ..                     LIB      PROD         Vern's working area
__    PACKTEST.MBR           MBR                   Test #pragma pack option
__    TEST.MBR               MBR

Notice, the first entry, a '.', means the directory you are in, and that
shows the physical file!!!
Next, '..' means the parent directory, adn that's a library
The remainder are the members of the "directory" listed at the top of the page.

Now, this ought to blow the minds of us pre-IFS dweebs, eh?

At 08:49 AM 11/8/02 -0600, you wrote:
>Booth,
>
>You said:
>A member is not a file.
>
>I realized recently on a project that, from an IFS point of view, members
>are manipulated like files, while our files are manipulated like
>directories.  For example, to delete a file in /qsys.lib, you'd actually use
>the RMVDIR RMVLNK(*YES) command to do it.  I suppose this is a consequence
>of using hfs commands in a non-hfs file system....
>
>Eric DeLong
>Sally Beauty Company
>MIS-Project Manager (BSG)
>940-898-7863 or ext. 1863
--