Re: Prompting from stored procedures, is this a thing?

["Alan (cfuture) Cassidy" <cfuture@xxxxxxxxxxx>]

I have maybe run an SQL statement maybe only once within CL. I don't bother with it anymore. It's unwieldy in my opinion. 

RPG makes it so much easier for prompting. 

--Alan Cassidy

> On 12/26/2024 5:11 PM EST David Gibbs via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote:
>
>  
> I really don’t think prompting from a stored procedure is a good idea. SQL
> is really meant to be a batch process.
>
>
>
>
> On Thu, Dec 26, 2024 at 2:54 PM Rob Berendt <robertowenberendt@xxxxxxxxx>
> wrote:
>
> > Here's the scenario.  You're checking a few things in your effort to switch
> > from one system to another.  This involves close to restricted state but
> > not quite.  ENDTCP and ENDSBS *ALL are out.  Client/server or http based
> > tooling are also out.  I thought about a CL based process but I have a lot
> > of SQL I want to use and I'm tired of jumping through hoops to interact
> > with SQL with CL.  I may end up with RPG.  I thought about using Stored
> > Procedures but prompting from that would be new to me (but I'm open to the
> > enlightenment).  I'm concerned that prompting from Stored procedures would
> > be as much jumping through hoops as using SQL from CL.
> -- 
> 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.