RE: Procedue with *varsize parm

[Alan Campin <Alan.Campin@xxxxxxxxxxxxx>]

How are you seeing these characters? With debug? If yes, what you probably
really seeing is the next set of characters in memory. You need to issue a
eval debug command with a %subst(variable,1, actual length of string) to see
just what is part of the string. If you define the *varsize parameter to be
say 100 bytes but only receive 15, the debugger has no idea what the real
length so it attempts to read 100 bytes and you will see what is in memory
following the the 15 byte string. 

You can use the CEEDOD function to determine the actual length. Please
contact me privately if you interested in the prototypes for the CEEDOD. 

-----Original Message-----
From: Chanh Le [mailto:Chanh_Le@countrywide.com]
Sent: Monday, November 29, 1999 4:21 PM
To: MIDRANGE-L@midrange.com
Subject: Procedue with *varsize parm





My procedure has a parameter with options(*varsize).  This parameter
receives the value passed in plus some extra characters like procedure
name.

I would like to know how to avoid these extra characters appended at the
end of this parm.



Thanks
CL


+---
| 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
+---
+---
| 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
+---