RE: Why did Stored Procedure execute?

[<tgarvey@xxxxxxxxxx>]

I'm afraid Jack may be right.
I just looked back at my storehouse of Stored Procedure source code. There
is no semi-colon at the end of the Create Procedure statement. Although all
my previous source had parameters (see example below), the semi-colon after
the End statement correctly ends the Create command.

Come on! Placement of a semi-colon caused my weekend nightmares!

Drop   Procedure LIBRARYNAM/BTUADelete; 
Create Procedure LIBRARYNAM/BTUADelete( 
    in UserID           char(10),       
    in TemplateMaster   char(10),       
    in CallingProgram   char(10)        
    )                                   
    language SQL                        
    modifies SQL data                   
    set option dbgview = *source        
                                        
Begin                                   
                                        
 declare TodayN      decimal(8,0);      

more statemenst...

End;


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jack
Woehr via MIDRANGE-L
Sent: Tuesday, February 7, 2023 10:46 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: Why did Stored Procedure execute?

Didin't the semicolon after the CREATE PROCEDURE end the CREATE?
And then the BEGIN stands there all alone and executes itself.
The CREATE PROCEDURE MYPROC should have been followed by a parentheses, not
a semicolon.
Right?!

On Tue, Feb 7, 2023 at 9:42 AM Birgitta Hauser <Hauser@xxxxxxxxxxxxxxx>
wrote:

> 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.