Re: Interactive SQL vs RUNSQL REQUEST submitted via AJS - syntax checking different -- MIDRANGE-L

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

Another option (not without its own pros and cons) is to put custom commands into their own library and then qualify the call:

TOOLS/MYCMD PARM(AVALUE)

As I said, pros and cons, but you'll see IBM doing this to force calls tot he QSYS version of commands.

If your sql statement goes into the parameter REQUEST you have the old
homegrown one with the concatenation bug.
If your sql statement goes into the parameter SQL you have the new one
supplied by IBM.

This is a caution to be aware of when you upgrade your OS!
It actually came out with some TR so that can be a concern also.

Some people go to great lengths to keep their existing code by renaming
the IBM one, etc.
I say sooner or later you are going to trip on your member so it's best to
fix your code to either use the IBM one or to rename the homegrown one and
redirect your code to use that one.

A stepping stone is to use the command exit point to intercept any use of
the "RUNSQL REQUEST" and log it and redirect it. Browse the log on
occasion and put that code on your to do list to get fixed.

Rob Berendt

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.