Re: Is there a better way to run SQL in a CL pgm?

I agree with you. The EXECSQL command I created was my first ever
experience with REXX and I was amazed at it's power and the fact that
nobody seemed to know anything about it except it was old and not used
anymore! I was sad when it was revealed that it was REXX that was the
problem when we opened that LPAR sorry Rob, PMR ( the weekend here is
already well underway!) because the only REXX procedure on our system was
dropped. I believe it was because the program using the rexx that run the
sql was called many, many times. In fact, wrongly in my opinion. I had to
send the REXX to IBM. Maybe that's where RUNSQL came from!

Le 30 mars 2012 18:16, John Yeung <gallium.arsenide@xxxxxxxxx> a écrit :

On Fri, Mar 30, 2012 at 10:44 AM, Dave <dfx1@xxxxxxxxxxxxxx> wrote:

Unfortunately there was an issue with REXX and SQL
after V6R1 in certain conditions.

Well, that doesn't change the fact that REXX has awesome string
handling and awesome integration with CL. So you can still just
compose your SQL string with REXX, and then issue the appropriate CL
command to invoke the SQL-executing tool of choice (in this case, the
OP is happy with RJS's DOCSQL).

Really, using "static" CL commands through REXX is virtually as simple
as using CL itself. (Just wrap your entire CL command in
double-quotes and you are done.) But when you want your CL command to
be dynamically composed, then REXX becomes way, way easier than CL,
because you can just intersperse your literal and variable portions
together (no *TCAT). It's ludicrously easy. And that's not even
touching on REXX's structured programming features and advanced
parsing, etc., etc., etc.

John
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.