RE: VARLEN field... what good are they?

[Buck Calabro <mcalabro@xxxxxxxxxxxx>]

It wouldn't be the first time I had things backwards!  :-)  Your example
makes it very clear.  I was thinking that you had VARLEN(31000) specified.
For those following this thread, there's one other thing you need to handle
variable length character fields: specify CVTOPT(*VARCHAR) either on your H
spec or on the actual CRTBNDRPG command.

Buck Calabro
Billing Concepts, Albany NY

> -----Original Message-----
> From: Stone, Brad V (TC) 
> Sent: Monday, May 17, 1999 12:01 PM
> To:   'MIDRANGE-L@midrange.com'
> Subject:      RE: VARLEN field... what good are they?
> 
> Actually, Buck, I think you have it backwards.  The max size goes in the
> field size and the minimum size goes in the first parm of the VARLEN
> keyword.
> 
> So, in my case, I had a field that was max of 31000 bytes, and wanted to
> specify at least 64 bytes.  So I specified...
> 
>  A            MHDATA     31000          VARLEN(64) TEXT('Message Data') 
> 
> 
+---
| 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
+---