On 17 Oct 2006 12:17:32 -0700, in bit.listserv.ibm-main you wrote: >Do you mean that every line on the file ends with an 0x0D? Or that you >have a line consisting of a single 0x0D after each data line? I.e. the >0x0D is on a line by itself?
Yep >If there is an extra 0x0D at the end of each line, then look at the file >on your UNIX machine. I will bet that there is an extra x0D there. To >me, this implies that somewhere along the line, there was an ASCII ftp >to a Windows machine (which uses 0x0A0D for a line end sequence) >followed by an BINARY ftp to a UNIX machine. > >I cannot prove the above, but it has been my experience in the past. That was my first guess before I even looked at the file. >Depending on what programs are available on your UNIX box, you might be >able to use the program "dos2unix" to remove the extra 0x0D on the UNIX >box before ftp'ing to the z/OS system. Another possibility if you don't >have "dos2unix"(not quite as nice) is to use the "tr" command on the >UNIX box to delete the 0x0D. This requires a command similar to: > >tr -d '\r' <input.file.with.x0Ds >output.file > >Then ftp the "output.file" to your z/OS system. Note that if you ftp >onto a z/OS UNIX file instead of a legacy dataset, you can run the "tr" >on the z/OS system, then use OCOPY or OGET to copy the data into a >legacy dataset (or use PATH= in your batch JCL to directly read the UNIX >file). Thanks ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
