A perfect example of why to convert from rpg cycle to free form using imbedded sql and procedures:
Brent would not even have to be concerned about learning the cycle if over the past 20 years someone had done so. And the argument continues ad infititum. Future "Brent"s shouldn't be faced with attempting to learn something that should no longer be there.
Yes, the RPG cycle is (or is it WAS) powerful and efficient coding wise. But after 25 plus years, I still don't like to convert or even maintain them. I don't fully understand it, and I don't really need it. I have yet to find ANY thing it does more than RPG used outside of the cycle, except with less code. But if less code is better, then SQL beats RPG.
And you are entirely incorrect concerning the control of SQL. The only reason to lose control of SQL is by not adhering to the same control you would need for an RPG programming, by using the proper controls that are needed to prevent loss of control.
However, training someone to use the RPG cycle who properly knows how to get the best of SQL should be considered pointless (IMHO). I don't know if Brent knows SQL, but lots of young people know it better than the RPG cycle and it might be better (in the future) to select from the pool of those who know SQL than to try to pick from the pool of those who understand the RPG cycle.
But the bottom line goes back to who cares what we think Brent needs, he doesn't answer to us. And he's probably very thankful for that. We're a bunch of "stuck-in-our-favorite" coders. And that works for us, but not necessarily for Brent.
My "two-cent's worth."
Duane
-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Thursday, April 27, 2017 2:38 PM
To: RPG programming on the IBM i (AS/400 and iSeries) <rpg400-l@xxxxxxxxxxxx>
Subject: Re: New to RPG
I truly fail to understand the abject terror some people seem to have about The Cycle. I can understand abject terror about doing mass updates via SQL, but not about The Cycle.
The nice thing about The Cycle is that you can use as much or as little as is appropriate to a given task.
I've written dozens of Cycle programs. I ride The Cycle anytime I need to pass through an entire file, and DO SO WITH A LEVEL OF CONTROL THAT IS NOT POSSIBLE WITH SQL.
With regard to using SQL to do some mass-update to a file, the VERY IDEA gives me nightmares. Using the SQL approach for that can SCREW UP A LOT OF RECORDS VERY FAST, WITH NO WAY TO HALT THE CARNAGE AT ONE DAMAGED RECORD. Using explicit reads in an explicit do-loop instead of what's already built into the language is sometimes necessary, to be sure, but often it just amounts to re-inventing the wheel.
Likewise, modern interactive programs tend to run inside an event-loop of some kind; The Cycle provides a perfectly serviceable built-in event-loop.
Level breaks? Secondary files? I can't recall ever using either one, and I certainly couldn't tell you how to do so (if I ever DID have a clue how they work).
But above all else, either ride The Cycle, or disable The Cycle, but NEVER, EVER, UNDER ANY CIRCUMSTANCES IGNORE IT. If you ignore it, one of two things will happen: either (a) your program will fail to compile, with a message to the effect that the compiler cannot determine how it will end, or (b) The Cycle will run you over.
--
JHHL
--
This is the RPG programming on the IBM i (AS/400 and 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.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD
CONFIDENTIALITY NOTICE: This electronic message transmission is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. If you have received this transmission, but are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this information is strictly prohibited. If you have received this e-mail in error, please contact NALC Health Benefit Plan at 703-729-4677 and delete and destroy the original message and all copies.
midrange.com
