× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I don't think the RPG Logic cycle was ever mandatory. But the lack of
iteration opcodes (DO, FOR, ITER, LEAVE) and the necessary reliance on
GOTO's made bypassing it painful.

Using the logic cycle and control breaks saved untold hours of programming
(and debugging) time. I have many customers unwilling to go to SQL solely
because they fear giving up L1; that's an education process on top with
thoughtful change management hidden underneath.

\reeve

On Thu, Jun 17, 2021 at 11:00 AM Justin Taylor <jtaylor.0ab@xxxxxxxxx>
wrote:

" why use RPGLE with cycle logic"

Beats me. My best guess is that it dates back to when the cycle was
mandatory.


date: Wed, 16 Jun 2021 14:56:56 -0500
from: Ignacio Garcia <cascada3405@xxxxxxxxx>
subject: Re: Commit & Logic cycle

Is a good idea....and why use RPGLE with cycle logic ?


--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.