Re: Chalk one up for "The Cycle"

["Tony Carolla" <carolla@xxxxxxxxx>]

Let me see if I understand.  You have a program that operates on every
record in a particular file, which you coded as a trigger program (not sure
why), and then you accomplished running the program by invoking the trigger
on every record?  Using the cycle?  Why not just write the program as a
non-trigger program, and tell it to operate on every record in the file?

On 4/25/07, James H. H. Lampert <jamesl@xxxxxxxxxxx> wrote:
> World's shortest RPG program:
>
> It seems that I had a problem with a trigger, used for
> data propagation. I was able to fix the trigger in such a
> way that to correct any given erroneous "target" record, I
> merely had to trip the trigger on the corresponding source
> record, and since the trigger would go on a "no-change"
> update operation, I didn't even have to do anything to the
> source record.
>
> Unfortunately, there were 192 affected records. And
> backtracking from an erroneous "target" record to the
> "source" record would take several minutes.
>
> Solution: a Cycle program (the names have been changed to
> protect the innocent):
>
> FFOOBAR    UP  AE             DISK
> C                   UPDATE    FOOBARREC
>
> That's all. Nothing else. Just two lines. And it rides
> through the file in a matter of seconds.
>
> Ain't The Cycle wonderful?
>
> --
> JHHL
> --
> 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.