AW: Why did Stored Procedure execute?

Jack
... the (SQL) Source code in a SQL Routine (Stored Procedure, Trigger and
User defined function) is always embedded in a compound statement (i.e.
between Begin and End) You may can refrain from the compound statement if
there is only a single statement to be executed in the routine.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
?Train people well enough so they can leave, treat them well enough so they
don't want to.? (Richard Branson)



-----Ursprüngliche Nachricht-----
Von: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] Im Auftrag
von Jack Woehr via MIDRANGE-L
Gesendet: Tuesday, 07.2 2023 17:30
An: Midrange Systems Technical Discussion
Cc: Jack Woehr
Betreff: Re: Why did Stored Procedure execute?

Because you ended the CREATE PROCEDURE statement with a semicolon, and then
inline in your SQL session you opened a clause with BEGIN.

On Tue, Feb 7, 2023 at 9:27 AM <tgarvey@xxxxxxxxxx> wrote:

Hi,



I may be about to expose my ignorance here but my skin is getting
thicker in my old age.

I wrote what I thought was a stored procedure that I could execute
later when I needed it. I ran the RUNSQLSTM command interactively to

compile it.

At first there were a few syntax errors that needed correction. Fixed
them but, when there were no errors, the procedure actually began

executing.

There is no Stored Procedure as an object in the library.



Here's the first few lines of that procedure.



DROP PROCEDURE UPILIB/COMPCONS;

CREATE PROCEDURE UPILIB/COMPCONS;

BEGIN

update Library/FileName set BICMPY = 72 where BICMPY in(20,71,90,95);



several hundred more lines.



END;



It's been a few months since I wrote a Stored procedure, but I don't
know how this thing could have executed with me actually calling it

separately.

What am I overlooking?





Kind Regards,



Thomas Garvey



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.