RE: Service Program and Signature/Rebind Question

Since all existing calls would have been required to pass all 5 parameters, then you shouldn't need to do that.
You can probably just go with an UPDSRVPGM and be fine.

Unless you changed more than just the options(*Nopass:*Omit).

Chris Hiebert
Senior Programmer/Analyst
Disclaimer: Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.


-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Robert Wenzel
Sent: Wednesday, December 20, 2017 8:40 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Service Program and Signature/Rebind Question

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.