RE: RPG Cycle (was Multi-Occurring DS)

The goal of moving away from RPGIII to ILERPG does not preclude using ALL the available techniques that it offers. An hour to learn/explain some of the older techniques might be well-spent, especially with appropriate comments with a reference to the manuals for future developers. That will usually take far less time than figuring out how to write a matching records routing or even level routines - an easier task in my opinion and necessary in other languages.

So I simply encourage learning the use of tools that make one's life easier - faster development, leaner code, all that. If MR is not one's choice, that's fine. But it's not fine, IMO, to say one should never use it.

Now when you start using SQL a lot, you might just HAVE to write your own MR routines!!

Regards
Vern

At 08:58 AM 12/19/2007, you wrote:

That is what I meant by depending on your IT goal and vision. It is
obviously wrong to say that nobody in my IT shop should use anything new
because Joe over here might not understand it. We are IT, it is our job
to keep ourselves updated. However, if your IT has already set a goal
to move away from RPGIII, for example, and is encouraging every
programmer to start using ILERPG, it would be counter productive for a
programmer keep insist that his brand new RPGIII application work just
fine, too bad if you don't understand it or not like it.

-snip-