Thanks, Paul. I think overall this is a good plan that you have laid out.
Barbara Baase
IBMi System i Administrator
Duro-Last Roofing, Inc.
525 Morley Drive
Saginaw, MI 48601
Phone: 989-753-6486 x2610
Fax: 989-753-4472
Confidentiality Notice:
This email, including attachments, may include confidential and/or
proprietary information, and may be used only by the person to whom or
entity to which it is addressed. If the reader of this email is not the
intended recipient or his/her authorized agent, the reader is hereby
notified that any dissemination, distribution, or copying of this email is
prohibited. If you have received this email in error, please notify the
sender by replying to this message, and then delete this email
immediately. Thank you.
From: PaulMmn <PaulMmn@xxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Cc: BBaase@xxxxxxxxxxxxx
Date: 08/14/2011 08:16 PM
Subject: Re: EDTOBJAUT from a CL program
Sent by: midrange-l-bounces@xxxxxxxxxxxx
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
midrange.com
