AGlauser@xxxxxxxxxxxx wrote:

Unless you create a new signature without making the existing signature a *PRV entry? Wouldn't that stop any programs that were not rebound from calling the *SRVPGM? I was thinking that this strategy could be used if you removed a procedure from a *SRVPGM, or changed the order of the procedures for some reason - just in case you missed anything when doing your UPDPGMs.


You're right, if you don't continue to provide the old signature, existing programs would get a signature violation.

But if I wanted to remove a procedure from a *SRVPGM, I'd just change it so it gave an exception when it was called. That way, programs that weren't calling it would still run fine.

I can't think of any reason to change the order of the procedures that would make it worth the hassle.

Ideally, changes to service programs should never require any UPDPGMs.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.