×
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.
Mark S. Waterbury wrote:
Only when the "interface" (procedure names, number of parameters, etc.)
changes, will you need to recompile and re-bind any callers of the
changed procedure(s).
Short version:
I think it's a good idea to use binder language right out of the gate.
Long version:
IIRC, the automatically generated signature of a *SRVPGM relies on the
names of the procedures and by extension the total number of procedures,
but not the number of parameters in any of the procedures. I think
that's worth pointing out, because the signature will not save you if
you add parameters but forget to rebind some callers.
If you add a *NOPASS parameter to a procedure interface, you technically
only need to rebind the callers that use the new parameter. I'm not
sure what would happen if you removed a parameter without rebinding the
callers.
Using binder language, it is also possible to add procedures to a
*SRVPGM without rebinding all of the users of that *SRVPGM. This can be
particularly nice when you're just starting out with *SRVPGMs, as you
may tend to add procedures quite frequently.
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
