Re: UPDSRVPGM

For the signature I use my name followed by today's date

El jue, 16 de nov de 2023, 14:21, Brian Parkins <goodprophet.bp@xxxxxxxxx>
escribió:

UPDSRVPGM only allows you to "snap in" a replacement *MODULE. There is
no way to add a new *MODULE to an existing *SRVPGM - it has to be
re-created with CRTSRVPGM. (No need to delete - the CRTSRVPGM has the
REPLACE(*YES) option.)

The Binder Source allows you the flexibility of managing the Signature
of the *SRVPGM such that you wouldn't (normally) re-create all dependent
*PGMs/*SRVPGMs which reference it - UNLESS they are calling procedures
in the new (added) *MODULE. It does this through the use of multiple
*PRV Signatures, (for backward compatibility) as well as the *CURRENT
Signature.

GOLDEN RULE: Add new exports to the end of the STRPGMEXP/ENDPGMEXP block.

(An alternative approach is to manually control the SIGNATURE on the
STRPGMEXP binder source statement by replacing *GEN with your chosen
hex/character string.)

HTH,
Brian.

On 16/11/2023 17:01, Greg Wilburn wrote:

So my question is this...
If UPDSRVPGM won't work when adding a module, do I need to delete and

recreate the SRVPGM?

Would I need to recompile all the programs that reference it?

I have a similar service program (7 modules) - I don't recall having to

do the latter.

Thanks,
Greg

--
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.