×
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.
Coyle, Stephen F. wrote:
What you describe is exactly what I do. When you say "probably
unnecessary" I was confused. Wouldn't you have to create a new current
signature so the new programs could use the new parameter, while leaving
existing programs to use *PRV?
Creating a new *PRV signature doesn't have any effect (positive or
negative) on the way the service program operates for programs that were
not rebound. The new signature just provides visual documentation of
which version of the service program that the program was bound to.
The srvpgm signature doesn't include any information about the nature or
number of the parameters, so if you are creating a new signature because
you think it will protect your srvpgm procedures from being called
incorrectly, you shouldn't bother. (If you are doing it for reasons
similar to Buck, go ahead, but don't count on any protection.)
Or can a *NOPASS parameter be added to a PI and existing programs not
using this parm will run fine as long as the procedure doesn't reference
the new parm?
Exactly.
As an Amazon Associate we earn from qualifying purchases.
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.