Hi, Joel:

Just to add to what Vern said, I strongly advise against adding any "private" authorities to objects, especially in a "production" environment.

What is much better is to create an authorization list for the entire library, perhaps with the same name as the library name, and then specify that name as the value for the CRTAUT parameter on the CHGLIB command. That way, whenever a new object is created in that library, it will be automatically assigned to that authorization list. Then, you can maintain any "private authorities" within the authorization list itself. This has many advantages, both from a performance point of view (speeds up authority look-ups) and simplifying maintenance, because updating private authorities on the actual object itself requires obtaining a lock on the object, and this may not be possible while the object is "in use" in a "live" production environment (during the day). ("Any problem in computer science can be solved by adding one more level of indirection.")

Note that this method (changing the CRTAUT attribute via CHGLIB) will not automatically take care of objects that get "restored" into that library. So you may still need additional tools, such as a good change management tool or product, to assist with that.

Hope that helps,

Mark S. Waterbury

> On 12/31/2013 12:43 PM, Vernon Hamberg wrote:
Hi Joel

Do you want to grant authority to a particular user, or to *PUBLIC?

If *PUBLIC, there is a setting on the library - CRTAUT - that is usually
set to *SYSVAL - that system value is QSYSVAL.

But you can use CHGLIB to change that attribute. I don't suggest
changing the system value. :)


On 12/31/2013 11:29 AM, Stone, Joel wrote:
Sally creates a file FILE1 in TESTLIB and forgets to GRTOBJAUT.

What is a simple method of having os400 do a default GRTOBJAUT for any obj created in TESTLIB?


This outbound email has been scanned for all viruses by the MessageLabs Skyscan service.
For more information please visit http://www.symanteccloud.com

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].