Re: Subfile performance question

Rick,
A very loooooong time ago, back in the early days of the S/38 (yes, I was there on R0.5), the hardware was not fast enough to keep up with the OS functions. Among those was subfile processing. Back then, there was in fact a severe performance impact of letting the system handle any part of the roll function, so we coded it ourselves.
Today, using the proper type of subfile, there is no reason to not let the system handle at least the roll back function (provided that your prior data is static).
A load all subfile, where the system handles everything, is good when you have a limited amount of static data, and can get it to the user in a timely fashion.

Hope this trip back in memory lane helps.

Jeff Young
Sr. Programmer Analyst
IBM -e(logo) server Certified Systems Exper - iSeries Technical Solutions V5R2
IBM Certified Specialist- e(logo) server i5Series Technical Solutions Designer V5R3
IBM Certified Specialist- e(logo)server i5Series Technical Solutions Implementer V5R3








________________________________
From: "Rick.Chevalier@xxxxxxxxxxxxxxx" <Rick.Chevalier@xxxxxxxxxxxxxxx>
To: rpg400-l@xxxxxxxxxxxx
Sent: Thu, February 18, 2010 9:58:09 AM
Subject: RE: Subfile performance question

Thanks to all who replied.

I too think it stems from not using the proper type of subfile but my co-worker didn't think that was the case.

So, to summarize, no one knows of any reason why scrolling within a subfile would be faster if handled by the programmer in the RPG code instead of letting the system handle the scrolling. The only performance issues mentioned were those of populating a subfile with a large data set all at once instead of incrementally as the need arises.

Rick

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.