RE: Why we don't use procedures more (was MOVE opcode in freeform /strange behavior w/%editc)

Rick,
I'm in the same boat (except the part about the high hourly rate).  My
employer does allow us to use and investigate new technologies, and I've
been able to teach myself some of the new stuff, but we (5 programmers) are
constantly being given "top priority" projects with no breathing room,
therefore no time to spend teaching ourselves things.  I've been fortunate
(don't ask me why) to spend more time than my coworkers at learning
procedures (actually I think I've _made_ more time than they have) to learn,
but its hard with no one else to, as you put it, brainstorm with.  That is
why I love this and the RPGIV list - I have printed and saved volumes of
code and advise, and when I have time I'll go back and read it!! :)  The
idea of a class would be nice, but we have to pull teeth just to get a
half-day each at the local NES user group yearly meeting!.
Oh well, thanks for letting me blow off a small amount of steam.....

Kevin Monahan
Sr Programmer/Analyst
JL Hammett Co
781-848-1000 x1114
www.hammett.com


-----Original Message-----
From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]On
Behalf Of Richard B Baird
Sent: Thursday, February 28, 2002 12:24 PM
To: rpg400-l@midrange.com
Subject: Why we don't use procedures more (was MOVE opcode in freeform
/strange behavior w/%editc)



Bob, Nelson, et al,

I think I'm in the middle here, and I don't think I'm unique.  I
desperately want to start and continue using procedures more, but I have
had certain barriers in my way, such as the fact that I work on a lot of
legacy stuff, at a high hourly rate, and I don't feel I should spend my
clients money "learning new stuff" or adding , and the lack of a
peer/mentor whom I would work with daily to brainstorm on when and why
using a procedure is a good thing, and when it's just fluff.  I used to
have the time, and the peers to learn the new stuff, but I'm kinda 'lonely'
now.

And I'm not completely unfamiliar with the concept either:  for years and
years, I've segregated duplicate code to programs that I can call from
anywhere, just passing and returning parameters.  I do 90% of my new
programs in rpgiv, but I still use a plain call to these "service
programs".  I just don't bind or prototype them.

The ibm manuals seem to compound the problem because they tend to tell you
too much - i don't have the time to dig through them and can't see the
forest for the trees, so to speak.  I need to get to the meat of something,
bang it around a few times, then use the manuals for reference.

maybe an FAQ entry on "procedure prototyping 101" with step by step
explanations of the "how and why" of a simple procedure might help.

I think the vast majority of us would love to start using them, and would
if we had the backing of those who sign our checks and a jumpstart....

ttfn,

rick