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

The (U)pdate with the (A)dd designation on a (K)eyed file would probably a carryover from needing to check for unique keys prior to the add. If only checking the key prior to the record Add the file could be coded (I)nput with (A)dd. Also the Update could have been used for a Keyed Delete process prior to the Add. I also seem to remember that at one time the (O)utput file was not an "add to" but a "create/replace" process.

The real reason is probably that the program was cloned from another program that did perform an Update with Add. But since this file has no unique keys so I wouldn't think there would be a need to force the write to disk

George Smith

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Tuesday, June 06, 2017 7:03 PM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: Any legitimate reason for 'UF A E' file defn when output only?

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?

--
JHHL

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD