Re: EDTOBJAUT from a CL program

[PaulMmn <PaulMmn@xxxxxxxxxxxxx>]

Coming late to the party...

But if you haven't fixed the authority yet, consider creating an 
authorization list and shifting authority from the object to the 
authority list (and my spelling of the keywords may be off!):

RVKOBJAUT for users who are listed

GRTOBJAUT AUTL(*authorization list name)

CHGOBJAUT  USRPRF(*PUBLIC)  AUTHORITY(*AUTL)

Then edit the authorization list and add in the authority you used to 
list for every object in the library.

Advantages-- you can change authority for all objects secured by the 
list at once.

Disadvantages-- any profile that still need special authority still 
has to be granted authority for each individual object.  But this 
should be a small subset of the full list!

And also while you're at it-- create 2 authorization lists:  One for 
program-type objects (programs, display and print files, modules, 
service programs, etc.), and a second list for data-containing 
objects (files, tables, data areas, data queues, etc.)  This give you 
more control over different types of objects.  For example, you may 
want *PUBLIC to have *USE rights to programs, but not to files.

--Paul E Musselman
PaulMmn@xxxxxxxxxxxxxxxxxxxx