RE: Calling export procedure using QZRUCLSP - Problem with parmpass byValue

Thanks Barbara.

Do you mind explain why it wouldn't work when parm is defined to pass by value?
1. The doc only say to pass by char pointer.  In my CLLE program I pass the 
variable &BBCD by reference, which match what the doc ask for.

My guess is that because it is define to pass by value, the caller is 
resposible to move the value of the passing parm to the parm memory address in 
the procedure.  Since CL doesn't know to do that, it wouldn't work.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Barbara Morris
Sent: Monday, September 26, 2005 6:23 PM
<clip>
The only types that are valid to be passed by value using QZRUCLSP are
4-byte integer and pointer.
  - 10i 0 
  -   *

Any other types have to be passed by reference.  So it's impossible to
call this procedure using QZRUCLSP.  If you need the procedure in this
form, you could create a wrapper that has the piBBCD parameter passed by
reference, and have it call through to this procedure.

Under "Parameter Formats" in the API doc:
  Each array entry should be one of the following:
    1   The parameter is a BINARY(4) argument to be passed to the
procedure by value. 
    2   The parameter is a pointer value.
</clip>