A question about multi-module SRVPGM

I've just dig a little around but wasn't unable to get an hint on this.

basically, we've move long time ago to what we can call 'basic' service
program, i.e. a single Srvpgm based on as ingle module to perform most
useful tasks regarding some programming logic (i..e decode a customer, add
an order row, create an order header and so on).

Now we're moving toward more complex Many Module to One SrvPgm approach,
especially for wide application, to reduce mess and optimize source.

We're developing several modules that perform upate on a single/multiple
file and modules that do perform some calculation on the same file, and
planning to create a single SrvPgm

The idea was to have a activity-oriented Srvpgm so that when dealing with
something (i.e. actually, link customer order to supplier order) we've a
single point that refer to everithing is needed.

We often have a heavvy module (or more than one) that does all the update
to several file/call several other Srvpgm, and we have another module that
do calculations on the same file, wich is much 'lighter' .Mostly, file are
managed in a 'every function opens the file it need in not already open
and leave it open fo subsequently call' way.

The question is: if we call for a funcion defined in the 'smaller' module',
does the system have to do much more work than using tweo separate SrvPgm
??

This is not specifically a performance-related question: we're just
wondering if, for the System, would be no diff beteween the two approach,
or if we're wasting resources just to keep item in a sigle object.


Any hint will be appreciated.

--

Nicola Brion
Tech Fossil (Often called a Dinosaur) - ancient animal that make things to
work.

"Ogni volta che la gente è d'accordo con me, provo la sensazione di avere
torto."