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



Hi,

SQE only supports real SQL.

Query/400, OPNQRYF, RUNQRY and QQQQRY are no SQL interfaces either and are
not supported by the SQE. 
(and IMHO will never be supported)

QMQRY is based on SQL and therefore can be executed by the SQE.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them?  Not training them
and keeping them!"

-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Mark S. Waterbury
Gesendet: Sunday, April 01, 2007 16:09
An: Midrange Systems Technical Discussion
Betreff: Query/400 and SQE vs. CQE


Hello, all:

I read in a forum or newsgroup somewhere recently that when you run 
Query/400 queries, they can only use the "classic query engine" (CQE) ... I
suppose that would make sense, since Query/400 is such an old tool, 
and was written long before SQE came along.

On the other hand, I thought that all programs that do any kind of 
"query" on OS/400 or i5/OS (OPNQRYF, RUNQRY, STRQMQRY, etc.), all invoke 
QQQQRY (the main query engine API), and it decides (based on some 
criteria) whether to use the CQE or the new SQE.

Can anyone clarify this or shed some additional light on this?

Thanks.

Mark S. Waterbury

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.