×
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.
Sam
The developerworks page describes the preview - the final information is at
publib.boulder.ibm.com/infocenter/iseries/.../rbafy*runsql*.htm
I agree with Luis - SQL0104 is the right message - however, I find this
message to be not as helpful as it could - it tells you what the "token"
is that made it fail, not the position - sometimes there are several
instances of the "token".
There is an SQL statement analyzer that DOES give the position. I use
that in our DOCSQL command's validity checker. It's part of a product,
so I can't say much more than that. It's easy enough to do, of course.
As to being a diagnostic - that may be how it is reported in an
interactive command-line setting. Did you run it in a batch or
interactive program?
Oh, yeah - RUNSQL does NOT run a SELECT - so this is very much like
RUNSQLSTM, with that troublesome (IMHO) restriction.
HTH
Vern
On 11/13/2012 6: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
As an Amazon Associate we earn from qualifying purchases.
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.