In case you care, on a system created new at 7.2, with very little 'system
type' modifications, and recently upgraded to 7.3 shows
Object . . . . . . . : SYSROUTDEP
Library . . . . . : QSYS2
Object type . . . . : *FILE
Object
User Group Authority
*PUBLIC *CHANGE
QSYS *ALL
And, once again, only certain IBM API's can update it, irregardless of
your individual authority.
Allow read operation . . . . . . . . . . . : Yes
Allow write operation . . . . . . . . . . . : No
Allow update operation . . . . . . . . . . : ALWUPD *NO
Allow delete operation . . . . . . . . . . : ALWDLT *NO
So, even if you had *ALLOBJ, *SECADM, *IOSYSCFG, etc you still couldn't
run UPDDTA against it and add, change or delete rows.
Whomever is messing with security seems to have executed the Al Barsa
MAKEAMESS command.
If it was truly intentional there just has to be a better way to lock down
sql access.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: SQL0552 Not authorized to DROP PROCEDURE., (continued)
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.