Good point on the /IF /DEFINE
I have always used binding source to make sure that the signatures stay in the correct order as well.
I think then when you add new procedures to the bottom everything stays in-sync for existing programs to use the existing procedures.
Is that right ?
Regards,
Richard Schoen
Web:
http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
------------------------------
message: 3
date: Sat, 21 Mar 2026 10:21:09 +0000
from: Brian Parkins <goodprophet.bp@xxxxxxxxx>
subject: Re: RPG Service Program vs Include Source for Shared
Subprocedures and SQL Calls
Even under these circumstances a *SRVPGM <may> provide a solution.
Multiple versions of the same procedure can co-exist in a single
*SRVPGM, (provided the names are unique). The flexibility of Signatures
and the Export Symbol Table.
100% agree that *SRVPGMs are the better option; /COPY and /INCLUDE
should - in the main - be used only for Prototype inclusion, (with /IF,
/DEFINE, etc. as required).
Brian.
On 21/03/2026 05:22, Niels Liisberg wrote:
The is some exceptions: versioning - where different clients need different
versions at a certain point in time.
midrange.com
