Are you running the command only from a command line? It might not throw
an escape message there - some commands are like that. Try it in a program.
On 11/13/2012 4:38 PM, Sam_L wrote:
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.
On 11/13/2012 7:40 AM, Luis Rodriguez wrote:
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
mainly, to the need to translate it into several languages (and
multiple PTFs for them). It seems that the help text would arrive
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 :-)
IBM Certified Systems Expert — eServer i5 iSeries