× 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.



If my SP has a subprocedure with five required (non-null) parameters and I
change the last three parameters to be optional parameters by adding
*options(*nopass:*omit)
*does this constitute a parameter change that requires that I have to
re-bind every program that was bound to the Service Program? If yes, can I
avoid re-binding by changing the current signature block in the Binder
Language source to *PRV and create a new *CURRENT signature block with the
exact same list of EXPORT symbols? All the documentation I have read
describes replacing the *CURRENT block with *PRV and then creating a new
*CURRENT block in order to avoid re-binding all the existing callers but in
the examples that I have read this was done only when a new subprocedure
was created in the SP. Only one text I have read states that "if you make
changes to the parameters....you must rebind" but doesn't state what
constitutes a "change". I would assume changing the data type and/or
parameter length would definitely constitute a change but my question is
based on the parameter's "options" attributes. Thank you.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

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.