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



Unless you mean interactive SQL when you say SQL/400, there should be no difference. QM queries are simply SQL statements encapsulated in an object, so there is really no distinction here. Of course, the settings in F13 can affect things. But not because a file is built from DDS instead of SQL DDL.

OTOH, there might be an issue with multiple member files, but not much - I can't say for sure, as I don't remember and can't try anything right now.

Vern

At 08:33 AM 11/1/2005, you wrote:

On 10/31/05, Carel Teijgeler <coteijgeler@xxxxxxxxx> wrote:
>
> To answer your last question:
> In SQL/400 F13 option 1, you can change the output format (defaults to
> screen, value 3 is disk).


This is a good one to know, but for the purpose of using RUNSQLSTM to
process my SQL statements, this won't work.

I do not know if SQL/400 will write to DDS based files; I had problems with
> that in the past. QM queries will write into DDS based files.


Good news. I have direct proof that SQL/400 will write to DDS-defined files.

- Dan
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
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.