×
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.
It's cool that IBM includes RUNSQLSTM now. Of course, you know that you
never needed the dev kit to execute SQL statements - just use STRQMQRY.
Stored procedures were always callable, using the CALL function. And all
you need is a text editor (SEU or CODEEDIT) and the CRTQMQRY command.
Some tradeoffs
- STRQMQRY can execute only one statement at a time (you can put RUN
statements into a QM procedure). RUNSQLSTM lets you run multiples, but you
can't do a displayable SELECT.
- You can have replacement variables with STRQMQRY, not with RUNSQLSTM.
- STRQMQRY can be the basis, as described, for a command line SQL
processor, RUNSQLSTM requires a hard-coded source member
These are not good vs. bad considerations, just things to think about when
choosing an implementation or methodology.
Unfortunately, calling stored procedures generally has little use in CL -
you can't get directly at the result set, AFAIK.
Regards
Vern
At 05:05 PM 1/10/03 -0500, you wrote:
With newer versions of os, RUNSQLSTM is a gimmie, and you are not required
to have the dev kit.
Rob Berendt
midrange.com
