Tim,

If the program is just adding records to the file (file is opened for
output only), then database will default to blocking the added records
into a 4K buffer prior to actually writing (making visible to the system)
the added records.  I would guess that with your record size and add
activity, that it is taking about 5 - 8 minutes to fill this buffer.

An easy way to turn this buffering off is to use OVRDBF on the file,
and specify SEQONLY(*NO).  An alternative, depending on the language
you are using, is to simply define the key as UNIQUE which will force
SEQONLY(*NO) processing for most high level languages (though this may
not work if using SQL or OPNQRYF or ???).  Either approach may impact
the raw performance of the program (that is, more handoffs to data
management), though I suspect your program is not real I0 intensive
(for this file anyway) due to the time lag you are experiencing.

As a bit of a disclaimer, the 4K buffer is simply data managements
current default size.  This could of course change over time.

Bruce Vining

>
>Hello All,
>Here's a quick question.
>1. AS400 Physical File that holds multiple comments for an order#.  The key to
>this file is (order#) + (3/0 seq#).
>2. File has 1.7 million records in it.
>3. File has ACCESS PATH MAINTENANCE(*IMMED) when I do a DSPFD.
>4. Records are being added to this file and they do not actually end up at the
>end of the file until 5 - 8 minutes later.
>Is this normal?
>TIA
>Tim Truax
>

+---
| 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
+---


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