Re: CallP Versus Program 'CALL' -- RPG400-L

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

On Mon, 11 Feb 2013, at 14:53:06, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 2/11/2013 2:38 PM, Vernon Hamberg wrote:

I didn't see a test for a CALLP of an EXTPGM vs CALLP of EXTPROC.

As you know, CALLP is not "call procedure" - it is "call prototyped" and
can either be to a program or a procedure.

I'd expect CALLP - EXTPGM to perform about the same as a regular CALL.
But I've not tried it.

I see no appreciable difference in 100000 iterations between a CALL and
a CALLP of the same program prototyped as EXTPGM run in the same AG.

CALL PGM LR on: 242000
CALL PGM LR off: 228000
CALLP EXTPGM LR on: 225000
CALLP EXTPGM LR off: 211000

Under the covers - and assuming that any parms used match the proto there should not be any difference. The code the compiler generates should be identical.

For the earlier case with a variable used on the call - the variable one should be pretty much the same speed. Basically the logic is:

Name same as stored value?
- If not resolve the pointer and store new value.
Call using the pointer.

So if the name doesn't change, the only difference is the test. A tiny, tiny amount.

Jon Paris

www.partner400.com
www.SystemiDeveloper.com

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.