Re: getting error on this view

Chuck - I believe the "went fine" was MY comment when using the formatter - AND it seems that the OP did NOT put the AND in the right place - see his next post.

Please take a step back on your position on the formatter - granted, it's not an iSeries tool - but it did present itself as a fairly agnostic tool. Or maybe take no position on it, since the input given you was faulty.

As it turns out, I believe that the formatter was helpful. You may have your own opinion, albeit without having tried the tool. SQL syntax is SQL syntax, after all, and there seemed nothing proprietary in the OP's statement.

Now as to using RUNSQLSTM - the article on that was very brief - the OP could have put his statement into a source member and tried it with the option to merely do syntax checking (*SYN is the value of the parameter whose name I don't recall).

On 9/15/2013 3:15 PM, CRPence wrote:

Yet we were told that by your having "put the AND there <ed: where I
saw you needed an AND> and formatted again - it went fine." Thus if
what was implied by that commentary is true, then indeed, we know the
formatter used will not be useful to diagnose the improperly qualified
column references.? That is not to say "I told you so", but to
emphasize that any particular SQL /formatter/ might not be capable of
diagnosing problems with the DB2 for i SQL syntax... so the actual
database parser and syntax checker may be effectively required.

Regards, Chuck

On 15 Sep 2013 12:27, Vernon Hamberg wrote:

We don't know WHERE the OP put the missing AND - so we can't speak
to whether the formatter was useful or not.

On 9/15/2013 2:16 PM, CRPence wrote:

On 15 Sep 2013 10:14, Vernon Hamberg wrote:

<<SNIP>>
I put the AND there and formatted again - it went fine.

And that proves, that SQL formatter, is not entirely helpful with
regard to resolving the SQL5001 error :-(