× 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: Blocking I/O (was: Expensive op codes)
  • From: Dave Murvin <davem@xxxxxxxx>
  • Date: Sat, 23 Oct 1999 11:17:37 -0700
  • Organization: DRM Enterprises, Inc

>From what I read in the manuals (see "Sequential-Only Processing" in DB@ UDB 
>for
AS/400 Database Programming V4R4), a  News/400 article ("A Game Plan for
Performance" Sept. 1999) and various postings, the difference between SEQONLY 
and
NBRRCDS is as follows:

NBRRCDS controls the number of records that are moved as a unit between 
auxiliary
storage and main storage.  You should only be using this keyword for physical
files read sequentially and for input only logical files read sequentially where
the underlying physical file is ordered in the logical file sequence.  
Otherwise,
this can decrease performance due to buffers being flushed prematurely (read a
big block of records, process a record, flush the big block of records, read a
big block of records, etc.).

SEQONLY(*YES nnn) controls the number of records that are moved as a unit
between  main storage and your programs internal buffers.

My tests reading (READ op code)  the million+ record physical file did not show
much difference using the NBRRCDS keyword.  (341 records is a 64K block).

OVRDBF SEQONLY(*YES 341)
    Elapsed time 1:19, number of seconds 63
OVRDBF SEQONLY(*YES 341) NBRRCDS(341)
    Elapsed time 1:18, number of seconds 63

Same test with no overrides, using the default blocking of 4K buffer
    Elapsed time 2:44, number of seconds 112

The News/400 article also said that the reason that READE is slower is that the
compiler translates READE into QDBGETK (Get by Key) Machine Interface (MI)
program, which doesn't perform blocking.


Alan Campin wrote:

> <snip>
>
> As an aside here, do anybody understand the difference between "SEQ ONLY"
> and "NBRRCDS" on the OVRDBF command? I have got conflicting statement from
> IBM about this and the manuals don't seem clear. I thought I understood the
> SEQONLY and NBRRCDS but then got told it was the opposite of what I thought
> so not sure what to believe. Thanks.
>
> < big snip>

--
Dave Murvin
DRM Enterprises, Inc.
davem@drme.com


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-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-Ups:
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.