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



Tom, you put that so politely :-). Not only am I not entirely accurate, I am totally inaccurate. I was thinking implementation as opposed to actuality.

Apologies for any confusion I may have caused.

Excuse me now, my humble pie is starting to burn.

Paul

Tom Liotta wrote:
midrange-l-request@xxxxxxxxxxxx wrote:


9. Re: Authority to libraries (Paul Tuohy)

Adopted authority ( USRPRF(*OWNER) ) overrides *PUBLIC authority. If you have explicity excluded a profile from the library then adopted authority is not going to help.


Paul, I don't think this is entirely accurate. Can you elaborate?

I have library(TEST) where user WEAKUSER has been granted *EXCLUDE from the library object. I have the following TESTCL CLP:

dsplib TEST

crtdupobj FILE TEST *file TEST FILEx data(*YES)

The CLP is usrprf(*OWNER) and *PUBLIC *USE; I am the owner and library TEST is all mine. WEAKUSER also has explicit *EXCLUDE from FILE.

When WEAKUSER runs TESTCL without usrprf(*OWNER), it fails immediately at the dsplib with CPF2182, Not authorized to library TEST. But usrprf(*OWNER) lets it run to completion with no errors. FILEX is created and WEAKUSER is the owner -- of course, there's now nothing that WEAKUSER can do with it.

I have a second file in TEST that I'm not authorized to. If I change the crtdupobj to reference that file, then TESTCL fails at crtdupobj.

Are there further issues?

Tom Liotta





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.