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

On Fri, 27 Dec 2013 11:00:17 -0500, "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.

One consideration is whether the programs are going to change what
activation group they run in. If they are, that can cause problems
with various things regardless of whether you actually add any
procedures or not. Some areas of concerns are overrides and OVRQRYFs.

Apart from that, I'm in agreement with those who are pointing out that
testing a program with internal procedures isn't significantly
different from testing one without them.

External procedures are more work to start with, but actually simplify
testing in the long run because the callers are only concerned with
the inputs and outputs.

Ken
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.