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

It's a possible solution. However I'm tired and done trying to shoehorn
sql into cl by the methods you've outlined and others. I'd sooner call CL
commands from sql stored procedures. But, since prompting is tough from
stored procedures I'd rather write the whole thing in RPG.

On Fri, Dec 27, 2024 at 1:55 PM Sam_L <lennon_s_j@xxxxxxxxxxx> wrote:

Without understanding your situation, might this be a solution?

Make your SQL into stored procedures, and call them from CL. The SQL can
create files and/or send send escape messages you can monitor for in the
driving CL. You could even create a report by listing a file with QMQRY
or Query/400 with RUNQRY *NONE.

Just a thought, FWIW ...

On 12/26/2024 3:53 PM, Rob Berendt 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.