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


  1.  Home
  2. RPG400-L
  3. June 2017

Re: Any legitimate reason for 'UF A E' file defn when output only?

On Tue, Jun 6, 2017 at 8:02 PM, James H. H. Lampert
<jamesl@xxxxxxxxxxxxxxxxx> wrote:
On 6/6/17, 4:25 PM, Luis Rodriguez wrote:

If you define a file as "O", the file's fields don't get defined in the
input specs. If you define it as UF the fields are "automatically" defined
(lame excuse, I know)

So?
They still get automatically defined in the output specs. What difference
does it make, if you're only going to write the records?

I could have sworn I've seen field-not-defined errors that somehow
involved output-only fields. Maybe with the field on the
right-hand-side of an EVAL or something? But I don't have an actual
example in front of me and my memory could be wrong.

John Y.

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.