On Fri, 1 Feb 2008 18:59:47 -0600, Paul Gilmartin <[EMAIL PROTECTED]> wrote:
>On Fri, 1 Feb 2008 10:13:53 -0600, Mark Zelden wrote: >> >>A coworker of mine was looking for basically the same thing you want to >>do.. but MVS to zip file. Instead of using OCOPY to get the data set in >>an HFS prior to zip, I showed him how we can NFS mount the MVS data >>set and use JAR directly ... >> >Please show me, too! Does this work for TEXT files? I can't >get it right. If I use xlat(Y), the data appear in ASCII; >if I use xlat(N), the records are strung out with no >linefeeds. What options did you use? Is there an EBCDIC-to- >EBCDIC translation table defined? > The translation is sort of confusing using the NFS client and server on z/OS. For EBCDIC data you do need to use xlat(n). PARM xlat(n) prevents double translation from the server and client. So this will actually translate the data to ASCII. See the fine manual (NFS). My co-worker pointed out the same issue you are seeing with the records. I told him to open them in word and the data was formatted the way he expected - so there must be some indication there. I've seen the same issues using FTP. I assume this could be "fixed" by using tr (unix translate) or other method. I haven't actually looked at the data in hex to see what is really there. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- 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
