Re: SQL VS QUERY

[rob@xxxxxxxxx]

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
The only advantage that Query ever had over SQL was the ability to direct
mail merge with OV/400.  Since OV/400 went the way of the dodo bird that
is not a concern anymore.  When you have SQL you also get STRQM.  Which
can be configured to work like Query, or like SQL.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




"Bob Carl" <bcarl@knapheide.com>
Sent by: midrange-l-admin@midrange.com
10/10/2002 10:08 AM
Please respond to midrange-l


        To:     "Midrange Computing Technical NewsGroup for ISeries"
<midrange-l@midrange.com>
        cc:
        Fax to:
        Subject:        SQL VS QUERY


This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
My account is getting ready to purchase some sort of IBM ISeries Query
tool,
SQL tools, or both.  I have been asked to provide justification for
investment in the SQL tool over or in addition to Query.

Can you use SQL in a CL in the same fashion as query, such as to create a
file(Like OPNQRYF). I would think you can.  I am wondering if we can scrap
query all together in favor of SQL (RUNSQL). Right now we do not use SQL
for
anything but transferring data, such as in Excel or Client Access, but
considering its industry presence, it seems like a no-brainer.   Please
submit to me your best arguments for using SQL, and if it can replace
Query
completely and easily.

 Thanks in advance.

Bob Carl, Senior Systems Analyst
Knapheide Manufacturing Company
217-223-1848 Ext. 2397
Fax: 217-223-1947

--

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