Re: Adopted authority -- MIDRANGE-L

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

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 07/26/2016
12:02:07 PM:

For the general topic of _adopting authority_ the two values are
indeed related.

However, for _adopting authority_ of the owner of a specific-program,

with regard only to that specific-program, the two attributes are
unrelated in the following sense: the adoption [or lack thereof] of the
privileges by the owner of that specific-program will hold true,
*irrespective* the setting for the Use Adopted Authority (USEADPTAUT) on

that specific-program.

Sorry, but that doesn't help much because it sounds like you're
saying that USEADPAUT(*YES) is basically ignored for the current program
-- which, of course, is impossible or the setting wouldn't exist. So, how
should the following table be completed?

USRPRF | USEADPAUT | Resulting Authority
-------|-----------|---------------------
*USER | *NO | Current User Profile
*OWNER | *NO | Current Object Owner
*USER | *YES | ??
*OWNER | *YES | ??

Sincerely,

Dave Clark

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.