Re: Need some ammunition (Procedures vs. Sub-routines)

I've had some moderate success in the past introducing service programs,
procedures.

By creating a simple "utility" service program, to format dates and
numbers, perform validations, read csv files, etc.

The usefullness is then immediately apparent, and when something can't be
done in one line with standard RPGIV, such as formatting a date like
"dd-mm-yyyy" (*iso with hyphen), the choice is easy.

In think that a significant source of resistance (besides having to use
different syntax and concepts) is that if (actually, when) something goes
wrong, it's difficult to asses and fix the problem, because of lack of
understanding how everything works together (programs, modules, service
programs, procedures, binding directories, etc).


On Fri, Dec 27, 2013 at 5:00 PM, RPGLIST <rpglist@xxxxxxxxxxx> wrote:

I won't go into the entire lengthy and boring conversation I just had with
upper management, but I was basically told that under no circumstances am
I to add procedures to certain applications. The justification is that
by doing so, we will be required to re-test the entire system, payroll,
dispatch, load balancing, AP, AR, etc.

I however was provided an opportunity to make my case, and I have a list
of reasons, but I need every bit of ammunition I can come up, so any help
from ya'll would be cool.

Dutch


--
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.