Re: AW: CallP Versus Program 'CALL'

I gotcha Scott, and as always, I appreciate your wonderful input. This
does bring me to another question though, the use of CALLPRC in a CLLE.
How does it know where to find the bound procedure? I didn't see anywhere
in the documentation that it specifies using a BNDDIR, unless I'm missing
something, which is probably the case.

Right... but sometimes discussion threads change meaning over time, and
this one had meandered off into a discussion about when typing "CALLP"
was required, so I commented on that offshoot of the discussion.

CALLP is a very versatile tool. It can call *PGMs, like the ancient
CALL opcode can. When it does that, performance is the same as CALL
would be.

CALLP can also call ILE procedures/subprocedures. In this case, it
perfroms better than CALL, but equivalent to the (horrible) CALLB opcode.

CALLP can also call Java Methods. IF you're worried about performance,
I would avoid this option.

So, anyway, I think you can see that your question just isn't as simple
as you phrased it.




On 2/10/2013 10:58 AM, Rpglist wrote:

Thanks Scott I suppose I should have worded my post a little better
in the beginning. What I was trying to determine was I'd it faster
to use a procedure either externally or internally defined versus
coding it as a program and using the CALL 'program name'

--
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.