As I recall, you can't avoid them. You have to work around them. What I've done is pass the length of the actual data and substringed out the actual value in the procedure. Seems to me that a varsize field really occupies the maximum length you define, but offers you the "convenience" of using it for something shorter. The manual says you can also use operational descriptors, but if I remember correctly, it didn't work well for me under v3r7. Haven't tried it under v4r3. > -----Original Message----- > From: Chanh Le [mailto:Chanh_Le@countrywide.com] > Sent: Monday, November 29, 1999 3: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: > firstname.lastname@example.org > +--- > +--- | 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: email@example.com +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.