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



In message <3.0.32.19970912185859.006bf0a0@mail>, From Ambarish Bagali 
<as4_sup2@sriven.scs.co.in>, the following was written:
> 
> I Stopped  my program at the last line, I found the file being 
> populated. Could any body please tell me what exactly is happening?

Ambarish,

When you specify a file for output or input (not update), the system
will automatically block the i/o. The reason you didn't see your data
was that it was still in the output buffer. If you close the file, the
buffer will be flushed and you will be able to see what you've written.
Usually, buffering is OK. It can speed things up a lot. Sometimes
though, you really need to have the data written to disk right away.
This has usually happened to me when I needed to write to one access
path and then read the same data back in through another. In that case,
you can change either the file description or use OVRDBF to change
FRCRATIO (then number of write operations before output is forced to
disk) to a low number, or even to 1. Of course you could use FEOD to do
the same thing. It is useful if you are writing many records, but still
need to make sure that they've all been written before you exit from a
routine.

Pete


--
 - Pete Hall peteh@earth.inwave.com
http://www.inwave.com/~peteh/

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.