Re: Program vs Service Program Procedures

Hi Roger,

as others mentioned, there is not significant performance difference - of course there is, but it will only be significant over a very large amount of calls.

But the SRVPGM route is the way to go today. First, designing a single PGM for doing different database tasks does often involve calls with "operation code" and many optional parameters.

And - a PGM cannot "return" a value. You have to use "return parameters" to communicate back. But the calling ode looks so much nicer and is better readable when written like:

if not createOrderHeader(....);
// error handling
endif;

Instead of

createOrderHeader(....:result);
if result <> 'OK';
// error handling
endif;

And every procedure can have its own interface/parameter list - specific to the procedure.

So as I already said - SRVPGM is the way today.

HTH
Daniel

P.S.: If you need more help about SRVPGMs, binder language, binder directories, copy headers, ... just feel free to mail me.

Am 10.11.2023 um 04:44 schrieb Roger Harman <roger.harman@xxxxxxxxxxx>:

I wouldn't waste any time worrying about performance impacts. A well-designed interface via procedures will likely pay you back big time down the road. Some new customers will have a requirement that you could easily fulfill with a modular approach.

In 2014, I rewrote a very complex rebate type application using service programs and procedures - the previous version had all the logic replicated across many programs. Each version produced a slightly different total. Try explaining that to an auditor. The serviced programs standardized all the calcs and, eventually, ended up being called by a number of other programs developed later.

Roger Harman
COMMON Certified Application Developer - ILE RPG on IBM i on Power



-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Greg Wilburn
Sent: Thursday, November 9, 2023 1:51 PM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: Program vs Service Program Procedures

I have the need to write several different programs or procedures to update/create database files in our Order Entry system.
I'm debating whether to write separate RPG programs versus creating a Service Program to contain the same calls to Procedures.

Right now, I see little reason to "reuse" this logic elsewhere. I guess that could change in future as these will operate on our ERP Order Header and Order Detail files.

Is there any significant performance reason to use bound procedures instead of call to separate RPG programs?

I found some older posts on forums that indicate the difference is negligible.

Thanks,
Greg
[Logo]<https://www.totalbizfulfillment.com/> Greg Wilburn
Director of IT
301.895.3792 ext. 1231
301.895.3895 direct
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx<mailto:gwilburn@xxxxxxxxxxxxxxxxxxxxxxx>
1 Corporate Dr
Grantsville, MD 21536
http://www.totalbizfulfillment.com/<http://www.totalbizfulfillment.com/>
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.