Re: Slow opening CLP's?

Exactly!

CLLE subroutine <> subprocedure. Not even close. No parms, no return code, no local variable scoping.

Yes, CALLSUBR supports a "return code" but I consider that to be useless. It's just a another global variable and limited to 4-byte integer value.

Roger Harman
COMMON Certified Application Developer - ILE RPG on IBM i on Power

 
 





From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxx> on behalf of dlclark@xxxxxxxxxxxxxxxx <dlclark@xxxxxxxxxxxxxxxx>
Sent: Wednesday, February 8, 2017 8:02 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] Slow opening CLP's?
 
"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 02/08/2017 10:14:14 AM:

I don't think that's quite true, I use subprocedures in CL all the time.
There may be a confusion between a module (an ILE object that is bound

to

the program) and an internal in line subprocedure.  It's actually called

a

subroutine but the same thing happens.    In CL you use "CALLSUBR" ,
"SUBR", and "RTNSUBR", or "ENDSUBR".

        A CLLE subroutine is not the same thing as a subprocedure.  When a
subprocedure is called in RPG it gets its own call stack entry.  Executing
a subroutine in RPG does not create a new call stack entry.  Likewise, in
CLLE, calling a subroutine does not create a new call stack entry.

Sincerely,

Dave Clark