True a *USER can perform *SECADM tasks but there is a caveat; they must
also have the appropriate rights to the objects they are working on,
for
instance the user profile. User A has rights to users B, C, and D, but
not to E, F, and G. User A would would be able to work on B, C, and D.
User A would not be able to administer E, F, and G.

Jim, what command was used that lists the users and limits that list to four
profiles for user A?

Did you actually try changing any user who wasn't in that list? My
understanding is that *SECADM authority gives the right to change security
regardless of other contrived privileges to profiles. *EXCLUDE may (but
probably should not) override this.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"A diplomat is a man who always remembers a woman's birthday but never
remembers her age."
-- Robert Frost




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.