In COBOL, I would use something like:
DISPLAY HDTS-CUS-GBL-LOC-SLD-TO-TEXT(1:HDTS-CUS-GBL-LOC-SLD-TO-LEN)
'|'
HDTS-CUS-GBL-LOC-BIL-TO-TEXT(1: HDTS-CUS-GBL-LOC-BIL-TO-LEN)
UPON SYSOUT.
Well, actually I'd use the STRING verb more like (assume OUTPUT-RECORD is a
PIC X(27) or more.):
STRING HDTS-CUS-GBL-LOC-SLD-TO-TEXT DELIMITED BY HDTS-CUS-GBL-LOC-SLD-TO-LEN
'|' DELIMITED BY SIZE
HDTS-CUS-GBL-LOC-BIL-TO-TEXT DELIMITED BY
HDTS-CUS-GBL-LOC-BIL-TO-TEXT
INTO OUTPUT-RECORD
END-STRING
WRITE OUTPUT-FILE FROM OUTPUT-RECORD
END-WRITE
Or something akin to that. On the remote end, the length of the string is
whatever it it based on the number of characters in the delimited field.
Between the | symbols and/or the end-of-line for the last.
On Wed, Apr 15, 2015 at 3:50 PM, Ron Thomas <[email protected]> wrote:
> ok still i am not able to know how in that flat file there is a length
> field, how that is going to be interpeted in the SQL server side . the data
> is in binary and when we unload to a txt file that part won't be readable.
> so do we need to remove that field and send ? 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
