×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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 mailing list archive is Copyright 1997-2025 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.
midrange.com
