Re: Restricting Users with *ALLOBJ in the Advanced Job Scheduler

[PaulMmn <PaulMmn@xxxxxxxxxxxxx>]

I thought the check for *PUBLIC authority was closer to the top of the list....

--Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx



At 7:43 AM -0400 8/15/08, Michael Ryan wrote:
> Here's how I believe authority checking works. It's a short-circuit
> mechanism - the first satisfied scenario causes authority checking to
> stop:
>
> 1. User *ALLOBJ
> 2. User Private Authority
> 3. User on AUTL
> 4. Group *ALLOBJ
> 5. Group Private Authority
> 6. Group on AUTL
> 7. *PUBLIC