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

Subject: Re: RPG Service Program vs Include Source for Shared Subprocedures and SQL Calls
From: Brian Parkins <goodprophet.bp@xxxxxxxxx>
Date: Sat, 21 Mar 2026 10:21:09 +0000
List-archive: <https://archive.midrange.com/rpg400-l/>
List-post: <mailto:rpg400-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@lists.midrange.com?subject=unsubscribe>

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.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

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

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.