|
At 12:28 PM 3/19/02 -0500, you wrote: -snip- >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. Query management is a cross-platform technology. It certainly exists on mainframes. I don't know which came first, mainframe or 400, but I suspect mainframe. It may even be on OS/2 and AIX. But it is not first and foremost a 400 thing. I mean, source file record lengths of 91? and 162 for forms? QM queries made on mainframes can be IMPORTed to the 400. There's more in the Query Management Programming manual (not Query Manager, which is the front end to Query Management). Concerning joins, Query/400 only matches against the primary. Doesn't SQL have the capability to nest joins in nonlinear order? Or does it compress everything back to the primary anyway? >_______________________________________________ >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list >To post a message email: MIDRANGE-L@midrange.com >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l >or email: MIDRANGE-L-request@midrange.com >Before posting, please take a moment to review the archives >at http://archive.midrange.com/midrange-l.
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.