|
Dan, To answer your last question: In SQL/400 F13 option 1, you can change the output format (defaults to screen, value 3 is disk). 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. Regards, Carel Teijgeler *********** REPLY SEPARATOR *********** On 31-10-05 at 14:23 Dan wrote: >On 10/31/05, Douglas Handy <dhandy@xxxxxxxxx> wrote: >> >> Then why not use a SQL statement instead and do an INSERT INTO? The query >> optimizer is smart enough to use existing indexes for record selections. >True 'nuff. Seemed even a tad faster than the CPYF FROMKEY/TOKEY. Didn't >measure, but... > >INSERT INTO TESTLIB/CUSMAS >select * from PRODLIB/CUSMASL00 >where CSC# >= 61200000000 and CSC# <= 61299999999 > >When I first prompted on INSERT, it didn't bring up any options to SELECT >from another file. Is this what I think I've heard before referred to as a >sub-select? > >Also, is there an equivalent of CPYF's MBROPT(*REPLACE) in SQL? Or a CLRPFM >equivalent statement that can be run before the INSERT INTO?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.