Re: Picking up an AUTL for newly created objects

[Jim Oberholtzer <midrangel@xxxxxxxxxx>]

As John suggested you can just put the AUTL on the library, or if you 
need to be getting any object that is created regardless of it's 
location, build a program to read the audit journal.  Any time you see a 
create object, put the correct authority per your policy on it.

I use that technique to move objects pesky consultants (like myself) and 
occasionally employees create in libraries like QGPL, QUSRSYS, etc. into 
more appropriate locations.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 9/6/2011 3:17 PM, ADriver@xxxxxxxxxxxx wrote:
> Hi,
>
> Just wondering if anyone has any ideas on how to make sure a newly created object picks up the authority of other objects in that library (possibly a combination of private auth. and AUTL). Not talking about *PUBLIC authority.
>
> I was looking at maybe registering an exit program on some of the CRT* commands, but the issue I found is that there seems to be no CRTQRY command for instance. There is a CRTQMQRY command, but we have a few users that sue WRKQRY to create queries.
>
> I guess there is always the possibility of simply running a daily job that assigns the correct AUTL and/or private authorities to new objects, but I was hoping there is a way to do it at the point the object is created.
>
> Am I on the right track with command exits, or is there a better way to do this that anyone is aware of?
>
> Thanks
>
> Adam Driver
> IBM Certified Systems Administrator - System i
> Consultant - Infrastructure Technician
> Exacta Corporation
> 608.661.6697 ext 2581