Re: Service Program and Signature/Rebind Question

Just to clarify.

Changing number/type/sequence of parameters will _NEVER_ require compulsory re-binding because parameters have _ZERO_ impact on Service Program signatures.

What matters is that your called routine deals appropriately with the parameters - and in particular never attempts to reference any that were not passed. *Omit parms should only have their address tested for null - you cannot reference the in any other way.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Dec 20, 2017, at 3:39 PM, Robert Wenzel <robert.wenzel@xxxxxxxxx> wrote:

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

*Robert Wenzel, Software Engineer*
iSeries Applications Support and Development

[image: Inmar]
<https://www.inmar.com/?utm_source=email%20signature&utm_medium=email&utm_campaign=Associate%20Email%20Signature&utm_content=Inmar%20Logo>

robert.wenzel@xxxxxxxxx
635 Vine Street, Winston Salem, NC 27101
*p: 336-770-3478*
www.inmar.com
<https://www.inmar.com/?utm_source=email%20signature&utm_medium=email&utm_campaign=Associate%20Email%20Signature&utm_content=URL%20link>
| LinkedIn <https://www.linkedin.com/company/inmar> | Facebook
<https://www.facebook.com/inmarinc> | Twitter
<https://twitter.com/inmarinc>

--


********************************************



*Inmar Confidentiality Note*: This e-mail and any attachments are
confidential and intended to be viewed and used solely by the intended
recipient. If you are not the intended recipient, be aware that any
disclosure, dissemination, distribution, copying or use of this e-mail or
any attachment is prohibited. If you received this e-mail in error, please
notify us immediately by returning it to the sender and delete this copy
and all attachments from your system and destroy any printed copies. Thank
you for your cooperation.



*Notice of Protected Rights*: The removal of any copyright, trademark, or
proprietary legend contained in this e-mail or any attachment is prohibited
without the express, written permission of Inmar, Inc. Furthermore, the
intended recipient must maintain all copyright notices, trademarks, and
proprietary legends within this e-mail and any attachments in their
original form and location if the e-mail or any attachments are reproduced,
printed or distributed.



********************************************
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD