• Subject: Re: FEOD question.....
  • From: Bob Larkin <blarkin@xxxxxx>
  • Date: Sun, 24 Jan 1999 19:20:27 -0800

There is one situation where this could be a problem, but I do not think your's
If you are outputting to a file, writes may be blocked. A review of the compile
listing will show a message if blocking qill occur. I don't think outputting to 
logical will exhibit the same behavior. Also, updates cannot be blocked.

Julie wrote:

> Hi everyone....
> I was working on an RPG/400 interactive program that uses two keyed
> logicals, one update,  from the same PF,  all update(*immed), RISC
> system, no EOFDLY (if it makes a difference?) .  I was told by another
> programmer that because the RISC system is so fast that the program
> could write to the file and not get a read within the same pgm because
> the buffer has not been cleared and that a FEOD will prevent this.  Does
> this make sense to anyone???  P.S.  I did RTFM.      Thanks....   Julie
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: david@midrange.com
> +---

begin:          vcard
fn:             Bob Larkin
n:              Larkin;Bob
org:            <A HREF="HTTP://web.wt.net/~blarkin/">Larkin Computer Consulting</A>
adr:            <A HREF="http://web.wt.net/~blarkin/">Bob and Diana's Page</A>;;;Houston;TX;<A HREF="http://web.wt.net/~blarkin/">;United States
email;internet: blarkin@wt.net
title:          Systems Consultant
x-mozilla-cpt:  ;4104
x-mozilla-html: FALSE
version:        2.1
end:            vcard

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].