RE: CLLE calling RPGLE sends bad parms???

[Buck Calabro <Buck.Calabro@xxxxxxxxxxxx>]

Scott wrote:

>You're telling the CL program to pass
>the parameter by reference.  You're
>telling the RPG program to receive
>the parameter by value.

That is quite correct, but CL has limitations regarding passing a literal to
a CONST receiver.  You MUST pad the literal to it's full size, just like
calling from a command line -or- have the called procedure use CEEDED to
find the Real Length passed.  In other words, CL does not honour CONST; it
uses OPDESC.

CL Programming guide, Chapter 3. I Am Nailed To The Hull... er... Chapter 3.
Controlling Flow and Communicating between Programs and Procedures:

"When you use the CALLPRC command and pass character string constants, you
must specify the exact number of bytes, and pass exactly that number. The
called
procedure can use the information in the operational descriptor to determine
the
exact number of bytes passed. You can use the API CEEDOD to access the
operational descriptor."

The example that follows illustrates this very well although it calls a CL
procedure and not an RPG procedure.

ILE CL indeed.
  --buck