Re: Authorization lists and authorities

[Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>]

Yes, reducing SAVSECDTA time is a related goal.  This particular email 
was just a response to a question I asked about IBM's default when you 
specify an authorization list in the CRTAUT parameter of a library.  IBM 
defaults to adding private authority for the owner.  I just wondered if 
anyone could see a reason to not do that.

On 5/9/2020 4:22 PM, Jim Oberholtzer wrote:
> If I recall correctly, your original purpose for this thread was the length
> of time the *SAVSECDTA was taking.    Adding private authorities would be
> counter  to your project goals as it would increase the time that process
> would take.
>
> Plus the owner of the object has *ALL authority to the object anyway.
>
>
>
> On Sat, May 9, 2020 at 4:08 PM Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx> wrote:
>
> > Just as a followup, nobody has suggested a reason to include private
> > authority for the owner of the object.  So my go-to setup for an object
> > is a slight variation of the one I originally posted.  I'll remove all
> > private authority, perform all authorization via the authorization list,
> > including *PUBLIC *AUTL.
> >
> >
> > On 5/7/2020 10:34 AM, Joe Pluta wrote:
> > > Object secured by authorization list  . . . . . . . . . . . . MVXDATA
> > >
> > > Object
> > > User        Group Authority
> > > *PUBLIC *EXCLUDE