Re: SQL0552 Not authorized to DROP PROCEDURE.

Rob,

Answer below (nope). We have 12 Lpars, nothing here is "jacked-up" or
needing restore(s).

All authority changes that we made were documented and tested one by one...
and then undone or put back to original state as needed since our changes
weren't accomplishing anything.

Again, CRPence (Chuck), reminded me that the system audit journal would
give greater insight to authority issues and ultimately gave us the
specific table name we needed to hit.

All good now and thank you for your views - I respect and appreciate all
your contributions and banter here.






On Thu, Apr 21, 2016 at 5:36 AM, Rob Berendt <rob@xxxxxxxxx> wrote:

Joe,

Were you the one who had someone at their company run a CHGAUT,
recursively, from the root level thus affecting authority on all objects?

Nope.


If so, would it help if one of us here ran a query against authority of

all objects in QSYS, QSYS2, QHLPSYS, QUSRSYS (usual members of QSYSLIBL)
and then you could compare that with what you have set?
Many of us probably have modified the authority on a few objects. On my
systems I keep those in a startup program. This would allow me to
highlight exceptions.


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.