Re: Passing *varsize parameter to another procedure

[Vern Hamberg <vhamberg@xxxxxxxxxxx>]

IBM handle it using a separate parameter for the length in many 
"retrieve" APIs. You can declare the return variable with length = 1 and 
options(*varsize). This is Bruce V's recommendation. Then you send a 
second variable that says how long your parameter really is - the API 
uses that much to put its results into.

HTH
Vern

Lim Hock-Chai wrote:
> Ops, yes "without losing the original length" is what I meant.
>
> If you have OPDESC on your export procedure, you could use CEEDOD to
> figure out the length of *varsize parameter (No additional length param
> needed).  This work fine until I need to pass this *varsize parameter to
> another procedure that actually does the work.  In this case, this other
> procedure is getting the max size of the *varsize variable length.  I
> can go a round it, but the way that I'm doing it is quite "not so
> pretty".  Soooo, I just want how other handle this type of stuff.
>
>
>   
>
> "Kurt Anderson" <kurt.anderson@xxxxxxxxxxxxxx> wrote in message
> news:<mailman.1358.1225402213.13295.rpg400-l@xxxxxxxxxxxx>...
> Do you mean "without" losing the original length?
> It's my understanding that when you use *varsize you should be sending
> another parameter stating the length of the field.
>
> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Lim Hock-Chai
> Sent: Thursday, October 30, 2008 3:47 PM
> To: RPG programming on the AS400 / iSeries
> Subject: Passing *varsize parameter to another procedure
>
> Can somebody suggest the best way to pass a *varsize parameter to a
> *varsize parameter of another procedure with losing the original length
> of the variable?
>  
>