× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. April 2016

Re: SQL0552 Not authorized to DROP PROCEDURE.

On an IBM i 7.2 lpar I did the following
CRTUSRPRF DUMMY (only those parameters)
Signed on as DUMMY.
STRSQL
CREATE PROCEDURE ROB/DELETEME NOT DETERMINISTIC CONTAINS SQL
EXTERNAL PARAMETER STYLE GENERAL
Procedure DELETEME was created in ROB.
drop procedure rob/deleteme
DROP PROCEDURE statement complete.
F3

DSPOBJAUT OBJ(SYSPARMS) OBJTYPE(*FILE)
*PUBLIC is *CHANGE
But you have to understand NO ONE but an IBM API can update or change this
table!
DSPFD SYSPARMS
Allow read operation . . . . . . . . . . . : Yes
Allow write operation . . . . . . . . . . . : No
Allow update operation . . . . . . . . . . : ALWUPD *NO
Allow delete operation . . . . . . . . . . : ALWDLT *NO

They do the same trick on the history table for a temporal table.

So when you do the CREATE PROCEDURE or DROP PROCEDURE it is an IBM API
which updates this table.

Someone got into your system and just totally buggered it up without
knowing what they were doing.


Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2025 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.