×
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.
Jim
I think you expect too much to get a perfectly clean conversion to IBM i
syntax - set up your view as SERVER(*LOCALSYS) SYNTAX(*SERVER) and put
your own statement in there - I often get what I want out of STRSQL or
whatever, then paste it into the SQL tab in ViewPoint.
Are there issues? Yes. There are things SEQUEL can do with formatting
that are lost, in my experience, when going all the way with IBM i
syntax - like having edit codes in the column list of the SELECT statement.
Now maybe a request to do a better conversion is in order. RTVQMQRY does
a better job now and could be used as fuel to support an enhancement in
SEQUEL.
And the optimizer can take even some "messy" syntax and run it better
than what it was given - no always, but this isn't a huge issue for me.
LOL on walking out - our feet speak loudly about what we believe, eh?
Regards
Vern
On 2/18/2015 10:32 AM, Jim It wrote:
Jim
You have to use the *LOCALSYS server for SEQUEL to use SQE - if you have
lots of views built over time, they are not likely to be set for that
server.
If you want to use IBM i syntax, set the SYNTAX parameter to server when
SERVER is *LOCALSYS
Vern,
While you are partially correct, that *LOCALSYS will allow SQL statements to go to SQE, the problem is that SEQUEL attempts to translate the SEQUEL syntax into a valid DB2 for i syntax, but the translation is messy at best and does not utilize the latests join techniques.
Not that I don't like the product, but I have immediately walked out in the middle of an interview when I was told that SEQUEL was their primary tool.
Jim
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.