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



Agreed. But it gets worse. What bit you is that Query/400 uses blanks and
zeroes for defaults in the unmatched fields (or DDS DFT values). SQL, which
is the driver behind QMQRY, knows nothing of DDS and other default values.
Its default is NULL - probably an industry standard.

I also sense that IBM wants us all to go with SQL, and you can get a
similar interface to that with STRQM.

It's a mess. OPNQRYF, Query/400, and SQL all use essentially the same
engine down below, and could have the same functionality. They don't.

Of course, interactive SQL understands JOINs but does not have prompting
for them.

At 09:59 AM 3/19/02 -0500, you wrote:
>Sheesh, well I guess you answered my last question!  Would it really be that
>hard for IBM to "enhance" RTVQMQRY to get the SQL right on joins?  After
>all, isn't WRKQRY using SQL under the covers?
>
>Dan Bale
>SAMSA, Inc.
>989-790-0507
>DBale@SAMSA.com <mailto:DBale@SAMSA.com>
>   Quiquid latine dictum sit altum viditur.
>   (Whatever is said in Latin seems profound.)
>
>
>-----Original Message-----
>From: midrange-l-admin@midrange.com
>[mailto:midrange-l-admin@midrange.com]On Behalf Of Vernon Hamberg
>Sent: Tuesday, March 19, 2002 9:44 AM
>To: midrange-l@midrange.com
>Subject: RE: QUERY TO SQL
>
>
>RTVQMQRY does not handle the various joins properly. Here is the text from
>Query Management manual that pertains, from Chapter 12. Using Query/400
>Definition Information in Query Management:
>
> >If the acceptability of the Query/400 result depends on any of the
> >following, the Query Management
> >result will probably be unacceptable. Parenthesized phrases indicate the
> >potentially unacceptable
> >system action for each item:
> >­ Unmatched join with primary file (A matched join is performed)
> >­ Matched join with primary file (A matched join is performed)
>
>It will never create a JOIN specification, only the older WHERE cluse
>version for joins. But you can take the join criteria and convert it to the
>appropriate JOIN, Query type 2 -> left outer join, type 3 -> exception join.
>
>
>_______________________________________________
>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 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-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.