On Mon, 8 Sep 2014 08:12:43 -0500, Paul Gilmartin wrote: >On Mon, 8 Sep 2014 11:43:16 +0200, Werner Kuehnel wrote: > >>I have a file on a WIN server with variable data records in EBCDIC and the >>correct end-of-line marker of x'0D25'. In the end I need a file with >>LRECL=582, RECFM=VB. >> >>When I ftp this file binary with "quote site lrecl=582 recfm=fb" all >>records are written contigously in chunks of 582 bytes. A second ftp >>(within z/OS) then splits up the records at x'0D25', but additionally at >>byte 582, which is wrong when a record flows over into the next record. >>All attempts to get the right format failed up to now. >> >>Does anyone has an idea how to accomplish this? >> >Eek! How did you get such a file. It may have a correct (according to >the standard definition of IBM-1047 and ISO8859-1) line separator of >x'0D25', but z/OS prefers the incorrect x'0D15'. Is your binary FTP >to a UNIX file or to a legacy data set. > >I would FTP in binary to a z/OS UNIX file, then use tr(1) to convert >every x'25' to x'15' (and perhaps vice-versa), then use a common >utility to delete every x'0D at the end of a line'. The file is now a >conventional z/OS UNIX file. If I needed a legacy data set, I could >pre-allocate the target to FB 582 and use cp(1) to transfer to that. > >I hate EBCDIC! > >-- gil
FTP in binary to a z/OS UNIX file, then "todsn -l 0x0D25" ( http://www.dovetail.com/docs/coz/dsp-ref_todsn.html ) to a z/OS dataset Norbert Friemel ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
