Yes. Sorry I wasn't more explicit. The actual length of the data is inherent in the number of characters between the | symbols. I.e A|B is different from A |B because in the second case, there is a valid trailing blank. Of course, for some processes, the latter _might_ require explicit delimiting in " marks: "A "|"B".
Going somewhat afield, I think of pipe delimited as a variant of Comma Separate Values which are explicitly defined in RFC 4180, https://tools.ietf.org/html/rfc4180 . But I also know that there are incompatible implementations out there as well. Personally, I prefer tab delimited instead because the tab character is rarely valid in a text field, whereas a comma or even a pipe could be. And, use of tab delimited is easier for me to process in AWK or PERL. On Wed, Apr 15, 2015 at 2:43 PM, Ron Thomas <[email protected]> wrote: > Ok. The broken vertical bar gets transfered correctly. the thing i need > to know is when i send the file as a txt, the length field will be a binary > data, so what you are saying is they need to define the field as Varchar > and we need not send that length field right ? > > Thanks > Ron T > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- If you sent twitter messages while exploring, are you on a textpedition? He's about as useful as a wax frying pan. 10 to the 12th power microphones = 1 Megaphone Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
