RE: Re: Using QMQRY for SQL validation

Rory,

I missed the original post, so do not know the exact requirements.

If you are able to prepare the SQL statement, would that not be your 
validation? Perhaps the QSQPRCED API may be usefull. Do not think it can be run 
in CLP.

Just a thought.

Carel Teijgeler

*********** REPLY SEPARATOR  ***********

On 5-8-05 at 12:34 Hewitt, Rory wrote:

>Rob,
>
>>>Obviously you didn't catch the PROCESS(*SYN).
>
>>>Maybe you better take another look at the API also.  Frankly, I think 
>>>you're off base on that too.
>
>Yes, I DID catch the PROCESS(*SYN). But it's not what I need.
>
>Re-read my original email:
>
>>>Anyway, I would like to be able to allow users to use this QMQRY not
>just to run SQL
>>>statements, but to validate statements (not just syntax-checking, but
>ensuring that any 
>>>specified columns exist etc.).
>
>PROCESS(*SYN) performs SQL syntax-checking ONLY. PROCESS(*VLD) (where
>available) not only checks the syntax, but ALSO checks that all the
>relevant columns exist in the table. So specifying a syntactically valid
>statement which references columns which don't exist in a table will
>pass *SYN but will fail *VLD. Hell, *SYN will correctly validate a
>statement which refers to a non-existent table.
>
>THAT'S why I want *VLD processing.
>
>Rory
>
>-- 
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@xxxxxxxxxxxx
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/mailman/listinfo/midrange-l
>or email: MIDRANGE-L-request@xxxxxxxxxxxx
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.