Re: 2 calls to same program using different parameter lengths

On May 18, 2017, at 3:19 PM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:

On Thu, May 18, 2017 at 1:04 PM, Rob Berendt <rob@xxxxxxxxx> wrote:

Well, if you're completely comfortable changing out all your consumers of
that service program every time you change the signature on the service
program then all the more power to you.

​Rob,

You're missing Mark's point...

There's no value added by changing the signature, simply add the new export
at the end and you're done.

You _only_ need to change a hard coded signature when you want to force
every caller to be recompiled.

PGMLVL(*PRV) is only really needed when you have SIGNATURE(*GEN)

Save yourself lots of effort and just go from

STRPGMEXP PGMLVL(*CURRENT) LVLCHK(*YES) SIGNATURE('MYSRVPGM sig v1')
EXPORT SYMBOL("CA9804R")
ENDPGMEXP

To
STRPGMEXP PGMLVL(*CURRENT) LVLCHK(*YES) SIGNATURE('MYSRVPGM sig v1')
EXPORT SYMBOL("CA9804R")
EXPORT SYMBOL("MYNEWSUBPROCEDURE")
ENDPGMEXP



Charles
​
--
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: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://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