× 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.



>Don't you find it disconcerting that IBM makes
>you do this?

Maybe it's my age, but I don't expect IBM to do anything for me at all!

>Heck, it appears that, with enough work,
>one could print a query definition and
>create the correct matching SQL just
>from that.  Maybe even create a template
>so that it could be done with any query.

If I had a lot of queries to convert, I'd probably write my own tool to do
it, just as you suggest.

>if IBM truly wants to move us to SQL,
>they shouldn't saddle us with half-finished
>tool called RTVQMQRY.

Your point about moving to SQL is interesting.  My earliest recollection of
QMQRY is that it was intended as an API for advanced tool-builders to use to
write their own interface to query.  I may (just may?) be full of hot air,
but I don't think IBM ever intended RTVQMQRY and STRQMQRY to be daily-use
tools like the would like embedded SQL to be.

Perhaps a design change request to enhance RTVQMQRY would let them know that
there's demand!
  --buck


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

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.