×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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 mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
