Re: Using the SQL GRANT statement for EXECUTE on a Stored Procedure

[Vernon Hamberg <vhamberg@xxxxxxxxxxx>]

Hi Dave

Syntax has to include what kind of thing you are giving privileges to

GRANT EXECUTE ON FUNCTION SEL220SP1 TO PUBLIC;

I see 4 categories of the GRANT statement in the reference, for 1) 
functions and procedures 2) packages 3) tables 4) user-defined types.

interactive SQL (STRSQL) has prompt only for packages and tables, 
although I assume it will run the other 2. I don't use the OpsNav or 
iNav SQL thing much, so I don't know what prompting it has.

Later
Vern

At 05:31 PM 4/5/2006, you wrote:

> The following doesn't function from either Ops Nav or ISQL like it does
> in the rest of IBM's DB2s:
>
> GRANT EXECUTE ON SEL220SP1 TO PUBLIC;
>
> and ISQL Prompting for GRANT EXECUTE says, in essence,  "What the hell
> is that statement?"  I only know SELECT, INSERT, UPDATE, etc.,  when its
> clearly in the SQL Reference manual.
>
> In Run SQL Scripts I get:
>
> GRANT EXECUTE ON SEL220CLSP TO PUBLIC;
>
> SQL State: 42601
> Vendor Code: -104
> Message: [SQL0104] Token EXECUTE was not valid. Valid tokens: DELETE
> INDEX INSERT SELECT UPDATE REFERENCES ALTER. Cause . . . . . :   A
> syntax error was detected at token EXECUTE.   yada, yada, yada
>
> Is this an IBM DB2 or just a name-only?
>
> What gives?
>
> Thanks,
>
> Dave Odom
> --
> 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.