Re: Service Programs / Binding Directories / *DUPPROC

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 02/07/2018 04:59:28
PM:

On Feb 7, 2018, at 1:00 PM, dlclark@xxxxxxxxxxxxxxxx wrote:

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 02/07/2018

12:57:06

PM:

I would not have encountered this Brian because I would never put a
module in a binding directory.

If I remember correctly, the ability to list modules in binding
directories was intended as an easy method for building programs
from multiple modules. But few people do that - I certainly don't.

We have a program that is built from ~83 modules. That said...

We

are starting a project now to split those modules out each into their

own

service program (using *DEFER on the binding). Why? We need to

decrease

the size of the memory footprint for this program because it is
long-running and there are ~600 jobs that execute this program as its

main

process.

Since the memory for the program will be shared by all instances how
will this help Dave?

Really? All ~600 jobs share the memory for the program? Didn't
know that. All I can tell you is that our folks and some folks from IBM
looked at our system and said we needed to reduce the temporary storage
allocation required for these ~600 long-running jobs.


Sincerely,

Dave Clark