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



An additional benefit of using a SQL index is that, if your SQL statement
includes only the fields declared in the index, the DB manager will not
access the base table, resulting in faster accesses.

Regards,

Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries


On Fri, Jun 4, 2010 at 2:46 PM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:

Kurt,

Yes, having a logical with significantly less fields (or rather
significantly smaller total bytes per record) helps.

As far as blocking, do you actually need the READE for the high volume
situation? If not, simply make sure the specific logical you created
above isn't used.

Lastly, have you considered SQL?

If you can do your operation with a single statement, then great. But
even if you need to touch each row in the RPG you could use a
multi-row fetch to whip the pants off non-blocking RPG native I/O.

Charles

On Fri, Jun 4, 2010 at 2:12 PM, Kurt Anderson
<kurt.anderson@xxxxxxxxxxxxxx> wrote:
Hi all,

Lately I've been dealing with a new client that has a high volume of data
for us to process, so I've been looking at various ways to get things moving
a little faster.

I believe I've successfully implemented the use of SETOBJACC with the
help of Chuck Pence & Mark Waterbury (thanks guys).

Now, this may be grasping at straws, but in a high data volume situation,
should I see any benefit in restricting the fields in a LF to only the
fields used by the program? (In essence, going from record length of 438 to
138.) My brain says, "yes," but the logic under-the-covers may not match
the logic my brain uses to come to its conclusion.

I'm also curious about RPG blocking. This question mainly goes out to
people using file encapsulation service programs, but is obviously open to
anyone to answer. I have a file wrapped up in a service program. This
service program pretty much handles all I/O operations for the file. Now,
if all I want to do is loop through the file, it's not going to block read
because it has operations such as READE in the service program. I wish
block-reading would be determined at run-time (again, a wish without a full
understanding of the compiler does its thing). I'm curious how people have
circumvented this limitation?

Thanks,
Kurt Anderson
Sr. Programmer/Analyst
CustomCall Data Systems
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.


--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.



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.