I'm not sure about hex, but when you look at it in Octal (in Linux), on FTP'd file there is a \r (or CR value) followed by a \n (or LF value). On the SFTP'd file, there is only a \n (LF value). That is where it gets lost. The \n is supposed to be the LF but when it gets passed to z/OS, z/OS doesn't seem to recognize it and continues on with one long line. That is what I was wondering is if somewhere in the z/OS GET command you have to tell it to use LF and not CR. Is this where the TR command fits in or is there another way?
Right now the only other idea is to add the CR value back into the file, but I don't like the idea of modifying a production file by adding in the character. Thanks, Mary -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Wednesday, July 09, 2008 2:27 PM To: [email protected] Subject: Re: SFTP GET COMMAND QUESTION > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Yukus, Mary J CIV USMEPCOM > Sent: Wednesday, July 09, 2008 2:16 PM > To: [email protected] > Subject: SFTP GET COMMAND QUESTION > > I have a question regarding the GET command for FTP. We have > a file that > comes from UNIX (AIX) to zLINUX through an SFTP. We need to > get it to z/OS > via FTP (not SFTP). The SFTP file contains the new line > character, but not > the end of line character. When the GET command is issued > (via JCL on z/OS), > we only get the first line of the file since it can't find > the carriage > return character (CR). > > Is there a command that can be added to the GET command to > use the new line > character (LF) to force the file to a new line rather than > the carriage > return character? > Thanks, > Mary >From what little that I know of the sftp command, as implemented on UNIX and Windows, is that it does the equivalent of a BINARY transfer. What is the "new line" character you mentioned, in hex? I hope that is it 0x0A. If so, then doing an ASCII ftp from z/Linux to z/OS should result in a normal file. I ftp'ed from my Linux/Intel box to both a z/OS sequential dataset and a z/OS UNIX (HFS) file. Both were OK. If it ends in something else, then I'd determine what character it is on your z/Linux box and translate it to 0x0a (using the tr command) before ftp'ing it to z/OS. AIX should end its lines in LF (0x0a), not CR (0x0d). Windows ends lines with CRLF (0x0d0a) -- 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 ---------------------------------------------------------------------- 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
