Re: Starting out with sub-procedures

["Buck" <buck.calabro@xxxxxxxxxxxx>]

> Still not discussed by anyone yet is how to
> group and document these pieces
> so the function can be found later and reused.

Grouping is fluid; much like the decision on exactly how to group objects
into libraries.  Many people use functional groupings; STRING, DATE, TAX and
so on.  The TAX service program (or /COPY member if you haven't taken that
step yet) would hold a few or a dozen sub-procedures which apply to your tax
calculations.  The STRING service program hold your string manipulation
(toUpper, toLower, MixCase, etc.)

Documentation is the same bugaboo it has always been.  I use FNDSTRPDM and
search for key words when I'm looking for stuff.   This is easy, because
there aren't many service programs to look through.  I'd be astounded if
there someone has more than a dozen altogether.  Like Scott, most of my
sub-procedures are inline.  There just aren't that many with global enough
appeal that I actually reuse them.  In my case, most of my reusable stuff
falls into my TELEPHONE service program; stuff like isTollFree, isLocalCall,
isLDCall and so on.

You need a gentle push and then you'll discover that reading about it is
much worse than doing it.  May I suggest you take Simon's example and work
with that?  Actually doing it will probably be all it takes for that bell to
ring!  Go for it!!!
  --buck