RE: Chalk one up for "The Cycle"

It's not the complexity...for me personally I like being a control
freak...so I want to do all the controlling processes. Not to mention
that to someone just seeing the cycle for the first time...they're truly
lost since they can't (or won't) figure out how the program is doing the
control processing. That being said..i have used the cycle for some
quick & dirty work but will never use for a production app...


Thanks,
Tommy Holden


-----Original Message-----
From: rpg400-l-bounces+tommy.holden=hcahealthcare.com@xxxxxxxxxxxx
[mailto:rpg400-l-bounces+tommy.holden=hcahealthcare.com@xxxxxxxxxxxx] On
Behalf Of Booth Martin
Sent: Thursday, April 26, 2007 9:34 AM
To: RPG programming on the AS400 / iSeries
Subject: Re: Chalk one up for "The Cycle"

I do not understand the difficulty in learning the Cycle? People write
as if it is tough to understand. To my mind it essentially is a means
of doing the housekeeping for you. Just let the system open and close
files, read records, keep track of level breaks, and do the multi-file
processing. There's no need to create the same hamster wheel over and
over. Where is the complexity that scares everyone?



Raby, Steve wrote:

<snip>
What difference does it matter if it's the cycle or sql if the next

person in line to have a go at the

program doesn't understand the full function of RPG? Let's say he

used SQL, and the next programmer has no experience in SQL. Wouldn't
that waste just as much time as an SQL savy person who has no clue about
the cycle trying to modify a cycle program?<Snip>

But of course we should only learn new new things, not old new things.

<tic>

<Snip>
If you can't figure out the cycle, then pass the program to someone

that can figure it

out, or learn it so next time you know about it. It amazes me

sometimes

the lack of gumption to learn something new. Even if you don't like

it,

you should learn it in case you have to work with it.<snip>

Hear hear.

Steve