Re: Removing or replacing *inzsr with Dspecs

To add to that, Alan, Craig Rutledge has a tool that converts subroutines to procedures - once Wilson has tried a few of his own, he could use that FREE tool to see what Craig does - it's interesting, as I recall.

These tools can be excellent teaching devices - for example, IBM's CVTRPGSRC can help to see the basic differences between RPG III and RPG IV. Linoma's or Craig's tools can take things just that much farther - sometimes how much "farther" is under the programmer's control.

Vern

On 6/10/2014 9:54 AM, Alan Cassidy wrote:

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Schutte
Subject: Re: Removing or replacing *inzsr with Dspecs

But that's about as far as I would go with sub procedures in a main line program. If there's other code that I feel like should be in a sub-procedure that's imported through a module or service program. Judging by the comment you made about being out of the game for a while, this might be a little too for this thread

...

If Wilson is in learning mode, converting subroutines to subprocedures can be a good exercise for him for getting used to them. Such conversions are good for that.

I like the idea for general maintenance where it doesn't detract from your timelines. Some subroutines use variables defined only for their purpose, or re-use work fields defined globally. To practice at first, do it with a few of them.

Alan