Library Authority -- SECURITY400

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Library Authority
From: Mike <koldark@xxxxxxxxx>
Date: Thu, 14 Aug 2008 08:42:24 -0500
List-archive: <http://archive.midrange.com/security400>
List-help: <mailto:security400-request@midrange.com?subject=help>
List-id: Security Administration on the AS400 / iSeries <security400.midrange.com>
List-post: <mailto:security400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/security400>, <mailto:security400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/security400>, <mailto:security400-request@midrange.com?subject=unsubscribe>

I have another question I don't quite grasp. I know if I give someone
*exclude on a library; they can't do a thing. I also know giving them *use,
they can access the allowed objects within the library.

But what if we want to give them *ALL on an object within that library,
would they be able to delete that work file?

Also, if we have *EXCLUDE on a library. Then we have a logical in another
library pointing to a file within the secured library. Would that work? The
file in the locked library would have READ access only.

Follow-Ups:

Re: Library Authority , Jim Franz

This mailing list archive is Copyright 1997-2026 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.