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



This is an existing authority list, shipped with *public  has *use rights.
In the early days (and still) it can keep pc clients from browsing the
directory structure of QSYS.LIB. You can edit with edtobjaut and type *autl.
jim

----- Original Message -----
From: "Chuck Lewis" <clewis@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, April 17, 2003 11:39 AM
Subject: RE: Access to Internal AS/400-IFS via Web Browser


> Jim !
>
> Is this the deal that we changed back in the EARLY Windows days or was
that
> a data area that we added or something ? This seems vaguely familiar...
>
> So then if I gave Object Authority and List Mgt for QPWFSERVER to, say, me
> or QSECOFR than I should be able to see more than then what I was seeing
> under Windows Explorer, etc. ?
>
> Thanks !
>
> Chuck
>
> -----Original Message-----
> From: Jim Franz Sent: Thursday, April 17, 2003 9:19 AM
>
> Chuck - check the authorities on qpwfserver *autl. This controls which
users
> can see an "explorer's view" of the 400 qsys.lib file system.
> from the Info Center
> The QPWFSERVER is an authorization list (object type *AUTL) that provides
> additional access requirements for all objects in the QSYS.LIB file system
> being accessed through remote clients. The authorities specified in this
> authorization list apply to all objects within the QSYS.LIB file system.
>
> The default authority to this object is PUBLIC *USE authority. The
> administrator can use the EDTAUTL (Edit Authorization List) or WRKAUTL
(Work
> With Authorization List) commands to change the value of this authority.
The
> administrator can assign PUBLIC *EXCLUDE authority to the authorization
list
> so that the general public cannot access QSYS.LIB objects from remote
> clients.
>
> hth
> jim
>
>
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>



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.