Rick,
I think this sounds like a bit off... As far as I know, the ONLY reason
one might conclude such is if they load-all a subfile with too much
data. This is a common issue, where thousands of lines get added to a
subfile, making the application unusable. The idea is not to list
EVERYTHING, but to show them only what they are looking for. Filtering
to reduce a result set to manageable size resolves most performance
related issues with SFL, IMO.
Otherwise, loading page at a time can make sense with some applications,
such as ones that use scrollable cursors and so forth. IMO, subfile
performance is a non-issue with the modern systems. I try to code my
SFL applications for clarity and simplicity, and only address
performance when issues are identified. I found working with scroll
cursors in SFL programs will lead to very clean, lean, and efficient
code.
JMO,
-Eric DeLong
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of
Rick.Chevalier@xxxxxxxxxxxxxxx
Sent: Wednesday, February 17, 2010 10:55 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Subfile performance question
A coworker stated the other day that handling the page-up and page-down
of a subfile in the RPG program was more efficient than letting the
system handle the scrolling. They couldn't give an specific reason just
that 'that's what I have always been told'. It was news to me and I'm
having a hard time seeing how that would be true.
Does anyone have an information or links to information about the
scrolling efficiency of a subfile vs. scrolling in the RPG program? I
may write a couple of test programs to do some timings but thought I
would ask first. I don't write a lot of subfiles these days and writing
them would not be a simple task as my subfile skills are rusty.
Rick Chevalier
IT Software Solutions - Loan Servicing
[
http://www.americredit.com/images/acf_email_sig.gif]
817-525-7178 (w)
rick.chevalier@xxxxxxxxxxxxxxx<mailto:rick.chevalier@xxxxxxxxxxxxxxx>
________________________________
Privileged and Confidential. This e-mail, and any attachments there to,
is intended only for use by the addressee(s) named herein and may
contain privileged or confidential information. If you have received
this e-mail in error, please notify me immediately by a return e-mail
and delete this e-mail. You are hereby notified that any dissemination,
distribution or copying of this e-mail and/or any attachments thereto,
is strictly prohibited.
midrange.com
