|
Hi Some more questions about the stored procedures. Sample: DROP PROCEDURE DB2BETT001; CREATE PROCEDURE DB2BETT001 ( IN @EXTOYT CHAR (32) )LANGUAGE SQL MODIFIES SQL DATA BEGIN DELETE FROM LIBRARY01.FILE1 WHERE EXTOYT = @EXTOYT; END; 1. We don't need the 'DROP PROCEDURE' statement for the first time we are compiling it, but next time we will need it. So for the first time we have to comment the statement and then again uncomment it. Is there any other way to do this so that we don't need to compile it twice? 2. We are using following command to create the proc RUNSQLSTM SRCFILE(PROCLIB/QSQLSRC) SRCMBR(DB2BETT001) COMMIT(*NONE) NAMING(*SQL) DFTRDBCOL(DB2B) DYNUSRPRF(*OWNER) a) If we do COMMIT (*NONE), we don't need to put 'COMMIT' statement inside the Procedure. Is this right? b) Are we using right value for the DFTRDBCOL parameter? Thank you, Amitava -------------------------------------------------------- This message (including any attachments) is only for the use of the person(s) for whom it is intended. It may contain Mattel confidential, proprietary and/or trade secret information. If you are not the intended recipient, you should not copy, distribute or use this information for any purpose, and you should delete this message and inform the sender immediately.
As an Amazon Associate we earn from qualifying purchases.
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.