If you use the cp command you can do something like cp -F crnl ... dataset options .. file dataset
The exact syntax is in the book. Rob Schramm Senior Systems Consultant On Tue, Mar 24, 2015 at 1:38 PM, Kevin Landin <[email protected] > wrote: > Thank you for the responses. > > I could not find an OCOPY option that would fix CRLF, unless it was meant > for me to build a character conversion table to handle CR? We do not have > Info-ZIP installed, and are using the Java JAR command to perform the unzip. > > It appears the suggestion to run: > > tr -d "\r" <input.txt> input_tr.txt > > will provide what we need. Another option may be to run a SORT to perform > a character replacement after the data is moved from z/OS Unix files to > z/OS data sets. > > Thanks again for the suggestions, > Kevin Landin > > -----Original Message----- > From: Paul Gilmartin [mailto:[email protected]] > Sent: Thursday, March 19, 2015 12:26 PM > Subject: Re: CR on records using OCOPY converting from ASCII to EBCDIC > > On Thu, 19 Mar 2015 09:44:56 -0500, Kevin Landin wrote: > > >We FTP a zip file from a vendor as binary to a z/OS Unix file. ... > > ... > >Besides editing the file and removing the CR, is there a way to prevent > the CR from being written to the z/OS data set during the translation? > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
