Re: QADBIFLD versus DSPFFD OUTPUT(*OUTFILE) -- MIDRANGE-L

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

Subject: Re: QADBIFLD versus DSPFFD OUTPUT(*OUTFILE)
From: Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
Date: Tue, 05 Feb 2013 15:28:10 -0600
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Agreed - and in any case, use embedded SQL instead of RLA.

On 2/5/2013 3:03 PM, rob@xxxxxxxxx wrote:

Ok, perhaps there is a use or two where not all columns are in SYSCOLUMNS
which may be in QADBIFLD. But if you don't have to go straight to the
table use the view instead.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: QADBIFLD versus DSPFFD OUTPUT(*OUTFILE) , John Yeung

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.