Re: RUNSQL Command: Help & Escape Messages -- 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.

Luis,

SQL0104 is the correct message, but it a diagnostic. I think that if your statement fails, then you should get an escape message, and the developerWorks documentation seems to agree.

I'll do a little more experimentation, but so far I have failed to get it to throw an escape message.

I did not notice the comment link--thanks. Seems a reasonable explanation of the missing help.

Sam

On 11/13/2012 7:40 AM, Luis Rodriguez wrote:

Sam,

At the end of the developerWorks page you cited, there is a "Comments"
link. Of of those comments explains that the command has no Help Text due,
mainly, to the need to translate it into several languages (and providing
multiple PTFs for them). It seems that the help text would arrive with the
next release .

Also, did you check the command with a valid SQL statement that, for
instance, tried to use an invalid file name? SQL0104 is, I think, the
proper message for the statement you wrote :-)

Best Regards,

Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries

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.