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


  • Subject: RE: Calculating the number of records parameter for batch extract
  • From: Joel Fritz <JFritz@xxxxxxxxxxxxxxxx>
  • Date: Fri, 24 Mar 2000 08:35:40 -0800

I think it's 64K in v4, but I could be wrong.  4K is the system default, and
I believe 32K was the max for CISC machines.  I'd be interested in your
results, I've gone with the system default and calculated my own blocking. I
don't remember getting a huge performance boost although I enjoyed copying
the ovrdbf code from program to program.

> -----Original Message-----
> From: Colin Williams [mailto:colin.williams@technocrats.co.uk]
> Sent: Friday, March 24, 2000 3:55 AM
> To: 'MIDRANGE-L@midrange.com'
> Subject: Calculating the number of records parameter for 
> batch extract 
> 
> 
> I am running a batch extract on V4R2, and want to set the 
> optimum number
> of records to read in using 
> the SEQONLY parameter on OVRDBF. 
> 
> Is it 4K Divided by RCDLEN  or 32K divided RCDLEN? 
> I realise there are other factors to consider, but I am just 
> using this
> as a starting point.
> 
> 
+---
| 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.