Re: CallP Versus Program 'CALL'

At the risk of being pedantic, CALLP is not obsolete; it's just optional in free format RPG, much like EVAL. If you're not coding free format, you have to use CALLP, and you can actually still use it in /free.

As to moving everything to service programs, that's kind of like moving everything to SQL. It's an option, but not necessarily required or even desired in every case. There's nothing structurally wrong with a program call; the operating system does it pretty well, especially when you don't set on LR.

Joe

If you talking about performance of CALL vs CALLP both making a program
there should be no difference at all. CALLP is just interpreted by the
compiler to generate CALL or CALLB code based on what you are calling.

Having said that, you should not be doing either one. CALL, CALLB and CALLP
are all obsolete. What you should be doing is prototyping the program
calls.

d CreateBFile...
d pr ExtPgm('ABCPGM')
d PR_CustomerNumber...
d 8a Const
d PR_Amount...
d 7p 2 Const
/Free

CreateBFile('A0001':
12.50 )

/End-Free

And, of course, if we push it up to the next level, if we are building new
code we shouldn't be doing program calls. We should be encapsulating our
business logic in service programs and making procedure calls.