Re: Subfiles was RE: Chalk one up for "The Cycle"

I go one step farther. If the subfile is 9,999 lines long then that is more than 500 panels to page through. That is no longer usable to an end user. I fooled around a bit and found that at about 2,500 records a subfile was still usable if it had a scroll bar. So when I look at a subfile problem if there can be much over 2000 records I redesign and have major/minor subfiles, or either/or filter constraints. Usually that solves the design issue, and in practice it also fits well with end user needs.


Alan Shore wrote:

Steve
There ARE subfiles that will NEVER be more than 2 - 3 pages long (List of
account types that are defined as
d Accttype s 2 0

however, saying that, I've had to rectify subfile programs that will NEVER
be more than 2 - 3 pages long and then die when they attempt to write the
10,000 record to the sub-file. As this program is in PRODUCTION this
problem needs to be rectified IMMEDIATELY, and believe me I've come across
quite a few of these. It turns out that the original programmer was either
NOT thinking, or was just taking the easy way out.
All I'm saying is, when creating a subfile, look at the length of what the
major key to that subfile is. If theirs a CHANCE that there are 10,000 or
more combinations within that key, bite the bullet and write a page at a
time subfile.



Alan Shore

NBTY, Inc
(631) 244-2000 ext. 5019
AShore@xxxxxxxx
"If you're going through Hell, keep going" - Winston Churchill




rpg400-l-bounces@xxxxxxxxxxxx wrote on 04/27/2007 08:32:14 AM:

Last night whilst sipping my Manhattan on my deck (I find mint
juleps far too sweet) did I think about work?? Not in the slightest. :-)

But, on the subject of subfiles , I still find that a lot people,
even for the simplest of subfiles want to put in code to control the
scrolling, and want to build it page at a time even though they know
it will NEVER be more than 2-3 pages long. Happily, for me, I have
not had to build a subfile in years that cannot be built all in one
go and with the system handling everything, though I have had to
maintain a few of the others and what a pain it is. The standard for
my current shop is that if the subfile is over 999 lines long the
program will crash, that is the standard I didn't write it, so, for
one of the few times, on the programs I have changed I go against
the standard and don't allow the program to crash, hey maybe I am
one of those Rogue(or is it Rouge) Programmers that people are
talking about. :-)

Steve

-----Oorspronkelijk bericht-----
Van: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]Namens Jerry Adams
Verzonden: vrijdag 27 april 2007 15:10
Aan: RPG programming on the AS400 / iSeries
Onderwerp: Re: Chalk one up for "The Cycle"


Last night, while sipping a mint julep on my deck, I got to thinking
about the "non-cycle is more logical, intuitive." I have to agree with
the statement, though I occasionally write cycle programs in ILE RPG
(even with subprocedures - how sick is that?).


But, then, I remembered subfile programs. Though I write subfile
programs, no one has (yet) been able to convince me that subfiles are
"easy and intuitive" to understand. On the other hand I wrote subfile
programs on the /36. Since the /36 doesn't have the built-in
(cycle-like?) subfile stuff, everything (and I mean everything) had to
be coded in the routines.


As much of a pain as subfiles are to program (or maybe it's just me), I
haven't heard (and don't expect to hear) anyone wanting to code subfiles
outside the built in system logic and handling. I no longer write
subfiles "manually;" that would be pretty masochistic.


* Jerry C. Adams
*IBM System i5/iSeries Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
615.995.7024
fax
615.995.1201
email
jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



Mark Villa wrote:

I like the film industry analogy *much* better than the one I was
going to use, my spark plug wrench. Don't use it often but it's there
when needed and is the best tool for the job.

The cycle? Yes, just tell the newbies to think of it like "the
original 4GL" = some of the work is automated. They won't have to
crack a book.
And that the only problem with the language and utility is that MS did
not market it.

Putting SQL in production is more complex to QA IMHO. But when
considering multi-platform development it is obviously the preference
between these two.

It is when the rogue programmer _decides on their own_ to use

something

different that they cause problems. <<

<<-- I bet this rarely happens in the real world. lol


Mark

--
This is the RPG programming on the AS400 / iSeries (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 AS400 / iSeries (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.