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

RE: Authorization list api's

I am not sure that it is appropriate.  Adopted authority is not the 
problem.  Think of this scenario.  Authorization list AUTH1 has *PUBLIC as 
*USE.  USER1 is some funky user (anonymous ftp or some such animal). USER1 
is listed on that authorization list as *EXCLUDE.

Isn't the api called "The List Objects a User is Authorized to, Owns, or 
Is Primary Group of (QSYLOBJA) API"?  If so, if I called that asking for 
USER1 this user would not be "authorized" to AUTH1 would they?  Or would 
they, meaning does *EXCLUDE still count as being "authorized" to it?

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...
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.