Re: 2 calls to same program using different parameter lengths

<snip>
I couldn't get the calling program
to compile, with CPD5D02 (Definition not found for symbol 'CA9804R'.)
</snip>

Think these steps...

In your service program ensure that you specified the EXPORT keyword on
the 'P' spec (or whatever the free form version is).
P CA9804R B EXPORT

Create a separate source file such as QBNDSRC or QSRVSRC
Create a member in this source file named the same as your service
program.
You're going to learn a new language. Binder language. However it only
has three commands.
STRPGMEXP PGMLVL(*CURRENT) LVLCHK(*YES) SIGNATURE(*GEN)
EXPORT SYMBOL("CA9804R")
ENDPGMEXP
Just those three commands.
Depending on your standards you may want to start out with
STRPGMEXP PGMLVL(*CURRENT) LVLCHK(*YES) SIGNATURE(V001.001)
EXPORT SYMBOL("CA9804R")
ENDPGMEXP

Then if you add a new subprocedure to that service program
STRPGMEXP PGMLVL(*CURRENT) LVLCHK(*YES) SIGNATURE(V001.002)
EXPORT SYMBOL("CA9804R")
EXPORT SYMBOL("MYNEWSUBPROCEDURE")
ENDPGMEXP
STRPGMEXP PGMLVL(*CURRENT) LVLCHK(*YES) SIGNATURE(V001.001)
EXPORT SYMBOL("CA9804R")
ENDPGMEXP
These signatures are like a record format level check. If you don't do
binder language and you just compile your program with CRTSRVPGM
EXPORT(*ALL) you would have to recompile every consumer whenever you
change your service program. See DSPPGM PGM(myconsumer) DETAIL(*SRVPGM)
for the signatures involved. Even a program you thought used no service
program. Surprise! Yes it did.
Then when you do your CRTSRVPGM specify the above member in EXPORT(...)

CRTBNDDIR mylib/mybnddir
ADDBNDDIRE BNDDIR(MYLIB/MYBNDDIR) OBJ((MYLIB/MYSRVPGM *SRVPGM))

Then in your consumer you would have these lines (again, or whatever the
free form version is)
H Bnddir('MYLIB/MYBNDDIR':'QC2LE')
H ActGrp(*CALLER) DftActGrp(*NO)

Then when you compile your consumer it should find that symbol.




Rob Berendt