Re: Service Programs & Copy Source

I personally would add them the the existing /copy source, and make a
new/additional signature in the service program with the binder language so
old programs will use the old signature until recompiled.

As for your constants, etc like endpoints, other values, I used to make
them constants in source but remember if they change it will require a
recompile of everything.  So instead I make "control files" with a name and
value and make a simple getControlValue() function that does a simple SQL
on the control file to get the value... like this:

endpoint = getControlValue('AMAZON_BASE_URL');

This way if anything changes it's a simple file update.  I used to use data
areas before that and that turned into a headache with so many contants
that could change in the future for some functions with Google, Microsoft,
UPS, etc.

On Thu, Oct 16, 2025 at 8:49 AM Greg Wilburn <
[email protected]> wrote:

> I have a question related to the copy source associated with a service
> program I have for communicating with Amazon SP-API.  I've had this service
> pgm for quite a while for managing merchant fulfilled orders.
> I recently was asked to add the ability to get(buy) shipping labels.  I
> debated whether to create a standalone program vs. creating a separate
> service program vs. adding a procedure or two to the existing service
> program.
> Because the authentication and base URLs are the same (and the new
> procedure would be called from multiple programs), I decided to add it to
> the existing service program.
>
> Now, I'm wondering about the /copy source.  For better/worse it contains a
> lot of named constants, defined values (templates), and exported procedures
> that wouldn't be necessary (or relevant) in programs that call this new
> procedure.
>
> So my question... do I just add the new prototypes to the existing service
> program /copy source, OR should I create a second /copy source containing
> JUST the prototypes necessary (two of them) for the other programs.  Is
> that "OK" to do, or is it frowned upon?  I'm thinking about complexity,
> conflict of named constants, procedure names (no prefix), etc.
>
> Thoughts?
> Greg
> [Logo]<https://www.totalbizfulfillment.com/>    Greg Wilburn
> Director of IT
> 301.895.3792 ext. 1231
> 301.895.3895 direct
> [email protected]<mailto:[email protected]>
> 1 Corporate Dr
> Grantsville, MD 21536
> www.totalbizfulfillment.com<http://www.totalbizfulfillment.com>
> --
> 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.