RE: Program vs Service Program Procedures

INLR will be off...

I think I've decided to go with the procedure approach... just not sure if I should keep adding it to a large service program I already have.

-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Buck Calabro
Sent: Friday, November 10, 2023 11:19 AM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Program vs Service Program Procedures

On Fri, 10 Nov 2023 at 08:42, Greg Wilburn
<gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

In this case, the application is a browser replacement for our Order Entry - the front end is developed using CNX Valence App Builder, while the backend is SQLRPGLE. The processes I'm handling simply validate and create/update order header and detail files (called from the CNX Exit program). I was creating separate programs for each file (i.e. one to add/update the header, the detail, etc.) when the user clicks on "Save". The exit program passes a DS representing the entire record format with the new values.

I'm not sure how many service pgms I have on our system (quite a few)... the biggest one contains 78 procedures (7 separate modules) related to our ERP system. I was just going to add these new procedures to a module in that service pgm used for file updates. BUT, I wasn't sure how many procedures is "too many" within the same service program. Do I just add to that service program? Do I create another, separate service program?

It's tempting to write that the performance of an RPG sub-procedure is
generally better than an RPG MAIN, but there are some assumptions
bundled into that statement which should probably be made explicit.
But rather than blunder my way through a description of how the
compiler initialises automatic storage, and when, let me rather ask
this:

When planning new, separate programs for each file, will these
programs be returning to the caller with LR on or off?

--buck