×
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.
Murphy, Mark wrote:
As Scott said, you can't remove a procedure from a service program safely without invalidating the
entire signature, whether you are using *PRV or not.
I still don't understand why you would want to remove a procedure from a service program while it was
still being used by some programs.
The example could just have easily involved changing the order of the
exports, or adding a new export between some existing ones. The point
still stands: using *PRV is not any safer than hardcoding one signature
and sticking to it.
Overall, this discussion has crystallized for me that there are really
two options. You can either rebind every object that uses a SRVPGM when
any change to the exports occurs, or you can take a risk that someone
will specify the binder source incorrectly.
For out shop, the risk of an incorrect binder source making it to
production is relatively low, while the pain of "recompiling the world"
is relatively high.
This mailing list archive is Copyright 1997-2024 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
