• Subject: RPG cycle was Re: DOW & DOU
  • From: "James W. Kilgore" <qappdsn@xxxxxxx>
  • Date: Mon, 11 May 1998 10:33:45 -0700
  • Organization: Progressive Data Systems, Inc.



Stone, Brad V (TC) wrote:

> The cycle rules.  'Nuff said.
>

Tim,

Our primary use of the RPG cycle is for batch process where we subset the 
primary
file in the CL wrapper with an OPNQRYF.

This just about includes every listing program (which also takes advantage of
level breaks).  Come on, how sinnful can it be to use the cycle for listing the
G/L chart of accounts? Sure you can do it with a read cycle, you can code your
own level breaks, but why?

It could be that the shops that "never" use the cycle may be using shared ODP's
and need the loop to position the file cursor when running batch type work in an
interactive session.  Just a guess.

Another guess would be that some shops may not have enough people who understand
the cycle.  The automatic things that occur may be too subtle.  Like having a
level break call a subroutine at detail time and the same indicator call a
routine at total time, 300 pages later, and trying to remember that total time
occurs before detail time.  If you are coding your own level breaks the total
time routine would be called before the detail time routine explicitly within
lines of each other.

The cycle does rule, but the kingdom is getting smaller. <g>

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].