RE: [WEB400] A Library is an IFS Directory???

["Phil Groschwitz" <phil@xxxxxxxxxxxxxx>]

Also the QPWFSERVER authorization list, if set to public *exclude, prevented
CA V3R2 from allowing QSYS to list in Windows Explorer.

Phil



> -----Original Message-----
> From: web400-admin@midrange.com [mailto:web400-admin@midrange.com]On
> Behalf Of Joep Beckeringh
> Sent: Thursday, August 24, 2000 4:04 PM
> To: web400@midrange.com
> Subject: Re: [WEB400] A Library is an IFS Directory???
>
>
> ----- Original Message -----
> From: "Bartell, Aaron L. (TC)" <ALBartell@taylorcorp.com>
> To: <web400@midrange.com>
> Sent: Friday, August 24, 2001 3:17 PM
> Subject: RE: [WEB400] A Library is an IFS Directory???
>
>
> > Go into Windows Explorer and take a peak at Network Neighborhood.  You
> > should see an icon for any AS/400's that you have setup in Client Access
> in
> > there.  When you click on that link you now have access to the AS/400's
> many
> > file systems.  QSYS.LIB is the file system that we have all come to know
> > real well with the Library structure and all, but the rest of the IFS is
> > basically folder driven and you can dig down multiple levels unlike the
> > QSYS.LIB structure.
> >
> > If I have said anything out of turn somebody please correct me,
> > Aaron Bartell
>
> Well, because you are asking :-)
>
> Whether you actually see the QSYS.LIB depends.  When you are not using an
> older version of Client Access you see only (through Netserver) what the
> system administrator has explicitly defined as shared.  With the older
> versions of CA the default was everything; with Netserver the default is
> nothing.  You can see the difference when you have a lazy system
> administrator :-)
>
> Joep Beckeringh
>
>
>
> _______________________________________________
> This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
> To post a message email: WEB400@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/web400
> or email: WEB400-request@midrange.com
>
>
>