Pete, I just downloaded "Getting started with DB2 Web Query for System i"
redbook from :

http://www.redbooks.ibm.com/redpieces/abstracts/sg247214.html?Open

Haven't read it all and don't have the product yet, but from what I've read
so far the answer looks to be no, there is no enhanced query/400 to SQL
converter. Instead you have an option to integrate the existing query/400
query definition into the Web Query product. In essence, Web Query would
run RUNQRY command on the back end and integrate the result set within the
Web Query tool.

If my interpretation is correct, that would mean that you wouldn't
necessarily have to convert all your queries to true Web Query objects.
That would also mean that you'd still be using CQE on the back end. Nothing
wrong with that as long as performance is acceptable.

Overall, product looks intriguing. I'm going to ask our hardware guy to
order it to learn more when I get a chance. What got my attention is cross
system joins... something that can't be done natively in SQL, without
additional products of course.

Elvis

Mike Cain - DB2 for i5/OS Temporary Indexes - The Good, The Bad, The Ugly
October 16
2007 System i Fall Technical Conference | Orlando | November 4-7
Celebrating 10-Years of SQL Performance Excellence on IBM System i, eServer
iSeries and the server affectionately known as the AS/400

-----Original Message-----
Subject: Re: Making Matched Records with Primary File in Query an Outer
joininSQL

<snip>

I wonder how the new Web Query product is going to migrate existing
Query/400 queries (if it indeed does do that)? They must have a better
tool than RTVQMQRY .

</snip>

Pete


This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].