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



Yes, closing the file should force it to disk.
Likewise, you could use FEOD (without closing the file)
Or you could put BLOCK(*NO) on the F-spec.

I'm not sure you really meant FRCRATIO, did you? Perhaps you meant SEQONLY? But in any case, they shouldn't be needed if you're closing the file.

Alan Shore wrote:
Hi everyone

Hopefully the explanation of my problem will make sense

For USER01, In program A, a record is written to fileA
then seconds or minutes later,
For USER02, In program B the record is deleted from FileA before going into
program A, and writing the same record to fileA

The result is that the delete seems NOT to be working as it seems that I
end up with duplicate records (no unique key on fileA)

At first I thought that this might be a situation to use the FRCRATIO on
FileA within program A, but when I look into program A, the file is defined
with usropn, and the file is only opened when a write is required and then
immediately closed directly AFTER the write.
My understanding is that the buffer will be flushed when the file is
closed.

Is this correct, or do I need to use the FRCRATIO parameter on an OVRDBF

Thanks in advance for any help


Alan Shore
Programmer/Analyst, Distribution
E:AShore@xxxxxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill


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.