Re: RPG Service Program vs Include Source for Shared Subprocedures and SQL Calls

.. but service program signatures quickly becomes a nightmare for version
control.. yes you can … but.. first you had one problem with control the
version .. now for each signature you have yet an issue..

Been there - done that.. never again…

lør. 21. mar. 2026 kl. 18.21 skrev Brian Parkins <[email protected]>:

> 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.
>
> --
> This is the RPG programming on IBM i (RPG400-L) mailing list
> To post a message email: [email protected]
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: [email protected]
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/rpg400-l.
>
> Please contact [email protected] for any subscription related
> questions.
>
>
-- 
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: [email protected]
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: [email protected]
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact [email protected] for any subscription related questions.