|
Aaron, If the other profile you used has *ALLOBJ authority on the user profile setup, then the PUBLIC *EXCLUDE does not apply to them. Rich Loeber Kisco Information Systems http://www.kisco.com ------------------------------------------------------------------------ albartell wrote:
Hi all, I am trying to lock down a library so only one profile can access it. I did a WRKOBJ MYLIB and then option 2 to edit the authority and I changed it to PUBLIC *EXCLUDE and gave my profile *ALL. I then signed in with another profile that _should_ have been locked out of MYLIB but I was able to see the objects data. So what I am wondering is where I should start looking for object security on the iSeries documents and a document concerning best practices for limiting access to certain objects on the iSeries. I am a newbie when it comes to system admin functions so please be gentle with me :-) TIA, Aaron Bartell http://mowyourlawn.com <mailto:aaron@xxxxxxxxxxxxxxx> -- 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/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 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.