Re: Service Program and Signature/Rebind Question

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 12/20/2017 10:39:36
AM:

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.

I would not expect to have to create a new export block in binder
source -- even if you change parameter options or add additional
parameters to a service procedure (as long as you make those additional
parameters optional). Even adding additional exports to the end of the
*CURRENT export block does not *require* creating a new export block. We
don't and it is working just fine.

I also would not expect to have to rebind all referencing programs
in the situation you describe. The exception is only in the case that you
wish existing programs to take advantage of the new parameter options you
are specifying. Changing parameter data types, lengths, dimensions is a
whole different animal (of course).


Sincerely,

Dave Clark