> -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Michael Knigge > Sent: Thursday, March 20, 2008 10:27 AM > To: [email protected] > Subject: Re: Convert EBCDIC to ASCII in batch? > > Why do you want to convert it first and than transfer it? If you > transfer the file via FTP in ASCII-Mode, the file is > converted and CRLF > is appended to each record. > > > Bye, > MK
I guess that I should have said why I am looking at this. We have an ftp which fails consistently. Absolutely 100% reproducible. At the request of the Windows server people, I transferred the same file to the same, failing, server using BINARY mode. The file transfer succeeded. I immediately tried doing the exact same file to the same server using ASCII mode and it failed again. So, the next thing that the Windows people are likely to say will be: "Since the BINARY transfer succeeded and the ASCII one failed, the problem __must__ be with z/OS doing an ASCII transfer! Why don't you just convert the file to ASCII on your side, then do a BINARY ftp of the already converted file?" As we all know, z/OS is always the problem in a case such as this. This despite the following facts: 1) I can do the exact same transfer to another Windows ftp server just fine, consistently; 2) I can do the exact same transfer to a Linux server just fine; 3) I cannot transfer the same file from my desktop to the "failing" server (Windows desktop to Windows server); and 4) I cannot transfer the file from the "successful" Windows server to the "failing" Windows server (Windows server to Windows server). In case 3, I got the file to my desktop via ftp. When I then tried to ftp to the failing server, it failed. Oh, I also forgot to mention that I can ftp smaller files. The file being transferred is around 9 gig in size. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. ---------------------------------------------------------------------- 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
