Re: SQL statements in a SQL Stored Procedure.

Alan,

The SQL reference says that the drop statement "can be embedded in an
application program or issued interactively. It is an executable
statement that can be dynamically prepared."

But my understanding, is that static statements can only have
parameters in basically the WHERE clause. In other words, you can't
have a static statement of any kind that uses a parameter for the
table name. This is based upon experience, if somebody knows where
the rules are spelled out I'd be interested in seeing them.

HTH,
Charles


On Mon, Dec 21, 2009 at 4:58 PM, Alan Campin <alan0307d@xxxxxxxxx> wrote:

When you are executing SQL statements in an SQL Stored Procedure do you have
to execute any SQL statements dynamically? I assumed you could just include
the statements and the compiler would put in the calls automatically. Here
is stored procedure which does not work. It tries to find InSchemaName as
the variable name.

SET PATH "QSYS","QSYS2","SYSPROC","SYSIBMADM","G5DEV" ;
CREATE PROCEDURE G5DEV.DROPDEV (
       IN INSCHEMANAME CHAR(10) )
       LANGUAGE SQL
       SPECIFIC G5DEV.DROPDEV
       NOT DETERMINISTIC
       MODIFIES SQL DATA
       CALLED ON NULL INPUT
       SET OPTION  ALWBLK = *ALLREAD ,
       ALWCPYDTA = *OPTIMIZE ,
       COMMIT = *NONE ,
       DBGVIEW = *LIST ,
       CLOSQLCSR = *ENDMOD ,
       DECRESULT = (31, 31, 00) ,
       DFTRDBCOL = G5DEV ,
       DYNDFTCOL = *NO ,
       DYNUSRPRF = *USER ,
       SRTSEQ = *HEX
       BEGIN
DROP SCHEMA INSCHEMANAME CASCADE ;
END  ;

IBM is saying I must execute the DROP statement dynamically. That doesn't
make much sense to me that I would have to do that.

Thanks for the help.
--
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.