Re: Multiple parms to procedures

["David Morris" <dmorris@xxxxxxxxxxxxx>]

Venu,

You can only return a single value from a procedure.  However, that value can 
be a data structure.  I would recommend against using a data structure for this 
purpose because it is not as flexible as multiple parameters.  If a routine can 
receive an error I reserve the return variable for an error flag, unless a 
single value is returned which can be evaluated to determine if an error has 
occurred.  IE:  If a product ID cannot be blank then I would return product 
number directly in a GetProductID procedure.

I code input parms with CONST or VALUE where possible which is about 98% of the 
time.  The exceptions being variable sized fields that are likely to be passed 
as data structures.  In this case I might consider passing a pointer.  I try to 
code input parms first where possible because at least one will be required.

I code I/O parms without the CONST/VALUE.  One per variable.  I use *OMIT or 
*NOPASS if it might be useful to retrieve a subset of the values.  I always 
test using CEETSTA API and not %ADDR because of the restrictions on CONST/VALUE 
parms.

Beyond that I would recommend one prototype member per module.  I would bring 
that in with /copy.  Anyway, that is how I do it.  Most important is to 
document what you are doing and then be consistent.

David Morris

>>> VENU YAMAJALA  <venu_yamajala@goodyear.com> 07/16 1:05 PM >>>
Hi All,

 I am trying to find whether we can have a ILE procedure that returns multiple
values as output. Is so, how do we code in the prototype and how do we
distinguish between the incoming parameters and output parameters. TIA for any
help / suggestions.

Rgds
Vg

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---