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



On 1/19/07, Buck <kc2hiz@xxxxxxxxx> wrote:

>> Look in the FAQ for RUNSQLSTM and you'll find an old but useful utility
>> that lets you run any SQL statement from a CL command line.
>> http://faq.midrange.com
>
> I realize this is stretching way back, since it appears you were limited
to
> old RPG, but do you remember if there was a reason why you (or the
original
> author, in case you didn't touch that part of it) did not use the
maximum
> number of values on STRQMQRY's SETVAR parameter?  SETVAR allows up to 50
> variables, and each variable can hold 55 characters.

I honestly don't recall.  It could be something as goofy as a limitation
of V2 CL :-)


In the intervening 80 minutes since I posted my previous response, I had a
dumbfounding epiphany.  Why the h*ll am I attempting enhance something
created out of constraint-driven necessity from 20 years ago, when I could
create a command that could just take a statement, up to 5000 characters
(command's *CHAR max), and pass it to an RPG program and process it there?
No having to split the statement into 50-character blocks (good grief)!
Leave QMQRY totally out of the process!  Certainly, someone's invented that
wheel, don't you think?  If not, it shouldn't be difficult.  I'm thinking a
PREPARE thingy and monitoring for and returning messages from the SQL
processor.

Any thoughts before I take the dive?

- Dan

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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