× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

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:


I may be about to expose my ignorance here but my skin is getting thicker
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.




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

several hundred more lines.


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

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2023 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.