RE: Auth lists - library or object level

Thanks Rob,

I had forgotten about changing the CRTAUT at the library level which would
mean all new created objects would get the *AUTL applied automatically,
that makes management much easier.

I will need to do some testing based on your suggestions.

Thanks
Don

 

Don Brown

Senior Consultant
 
[1]OneTeam IT Pty Ltd
P: 1300 088 400

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob
Berendt
Sent: Tuesday, 25 November 2025 11:41 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Auth lists - library or object level

I would apply it to the library, and to all objects within the library.
Then I would change the library so that any new objects get that
authorization list GRTOBJAUT OBJ(mylib) OBJTYPE(*LIB) AUTL(myautl)
GRTOBJAUT OBJ(mylib) OBJTYPE(*LIB) USER(*PUBLIC) AUT(*AUTL) GRTOBJAUT
OBJ(mylib/*ALL) OBJTYPE(*ALL) AUTL(myautl) GRTOBJAUT OBJ(mylib/*ALL)
OBJTYPE(*ALL) USER(*PUBLIC) AUT(*AUTL) CHGLIB LIB(mylib) CRTAUT(myautl)

On Tue, Nov 25, 2025 at 5:08 AM Don Brown via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

> I am trying to find some examples of using authorisation lists and
> specifically from the point of view do I apply at the library level or
> the individual object level.
>
> For my requirement I think the library level will be perfect but I
> have done a little testing and not getting the results I expected.
>
> I have been searching for examples or a redbook but everything I have
> found just goes into haw to create a list and how to apply it to an
obkect.
>
> Hopefully someone will have a good link I can review.
>
> Thanks
>
> Don
>
>
> Brisbane - Sydney - Melbourne
>
>
> Don Brown
>
> Senior Consultant
>
>
>
>
> P: 1300 088 400
>
>
>
>
> DISCLAIMER. Before opening any attachments, check them for viruses and
> defects. This email and its attachments may contain confidential
> information. If you are not the intended recipient, please do not
> read, distribute or copy this email or its attachments but notify
> sender and delete it. Any views expressed in this email are those of
> the individual sender
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
> subscribe, unsubscribe, or change list options,
> visit: [2]https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives at
> [3]https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
> related questions.
>
>
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: [4]https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
[5]https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

--
Message protected by MailGuard: e-mail anti-virus, anti-spam and content
filtering.
[6]https://www.mailguard.com.au

References

Visible links
1. https://www.oneteamit.com.au/
2. https://lists.midrange.com/mailman/listinfo/midrange-l
3. https://archive.midrange.com/midrange-l.
4. https://lists.midrange.com/mailman/listinfo/midrange-l
5. https://archive.midrange.com/midrange-l.
6. https://www.mailguard.com.au/