Re: Possible timing issue with IO

On 26-Jan-2014 08:40 -0800, Vernon Hamberg wrote:

<<SNIP>> Hmm, just had a thought - I have to be sure that my
date/time is not too recent - that the upload date & time might not
be earlier than the last run of my cleanup.

Seems a more likely origin for the described difficulty, IMO, than the FEOD being discussed.

OK - having y'all for a blank wall is always helpful - will let you
know what's up - because it seems the FEOD should have worked.

Seems to me that "the FEOD should have worked" to ensure the records from the previously buffered WRITE activity [into the ODP] would have been made available in the physical dataspace and the maintained access paths, *if* the F-spec had instead been defined with File-Type=O [i.e. Output-only].

However given the File-Type=U [i.e. Update-file] and irrespective the File-Addition=A [i.e. to enable Add records to the DISK file], as was described in the scenario from the OP, the Force End of Data (FEOD) should not play any role. That is, the FEOD should have had no effect, just as was determined from testing. There also should not have been a message about RPG using buffered I/O as an effective reminder about the possible need for an FEOD on that file's ODP; i.e. no RNF7086 "RPG handles blocking for the file. INFDS is updated only when blocks of data are transferred." in the compiler listing.