RE: RPG Cycle (was Multi-Occurring DS)

It is not that simple. If you are used to conditioning, you have to
account for Total time level breaks that work outside of your detail
time logic and rules.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of James Lampert
Sent: Wednesday, December 19, 2007 1:43 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: RPG Cycle (was Multi-Occurring DS)

It might take me weeks to understand how to use control breaks or
matching records, as built into The Cycle. More trouble than it's worth
for me, which is why I do handle such things with my own code.

But understanding the basic premise that an RPG program will repeat
itself, implicitly reading from a file designated as "primary," until
either the LR indicator is set, or it encounters a RETURN statement (in
the latter case, terminating but remaining active)? If a programmer
needs more than two minutes to grasp that basic concept, the only one
you actually need in order to write and maintain the more basic sorts of

Cycle programs (especially the unconventional ones), then maybe he or
she is in the wrong line of work.