Re: Library Authority

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

yes - *USE on lib will allow delete of object in lib if user has delete auth to object.

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.

yes - (i've not tested this), note: data authorities on LF cannot be more than on PF.
(this one i was not positive till checking Woodbury/Botz's Experts Guide book p164)
jim franz


----- Original Message ----- From: "Mike" <koldark@xxxxxxxxx>
To: "Security Administration on the AS400 / iSeries" <security400@xxxxxxxxxxxx>
Sent: Thursday, August 14, 2008 9:42 AM
Subject: [Security400] Library Authority

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.

--
Mike Wills
Midrange Programmer/Analyst

Sick of corporate radio and hungry for something new?
http://thenextgenerationofradio.com
Stalking me? http://twitter.com/MikeWills | http://friendfeed.com/mikewills
_______________________________________________
This is the Security Administration on the AS400 / iSeries (Security400) mailing list
To post a message email: Security400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/security400
or email: Security400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/security400.