Re: FTP from I5 to Server with CRLF

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

If the i is your client software, and you're connecting to a Windows FTP 
server, then yes, LOCSITE TRIM is the appropriate method.

If your i is acting as the server, and you are using the Windows client, 
it'd be SITE TRIM.

Mary E Mallazzo wrote:
> Scott
> Found it I presume it is Locsite Trim 0?
>
>
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
> Sent: Wednesday, October 14, 2009 1:06 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: FTP from I5 to Server with CRLF
>
> Hello Mary,
>
> > So we inserted the CRLF and thus got the blank records....we have changed
> > the CRLF from  X'0d25'  to x'0D0A'...
>
> Just to be clear...  x'0d25' is the EBCDIC code for CRLF.  x'0d0a' is 
> the ASCII (and UTF-8) code for CRLF.
>
> If your program is translating all of it's data to ASCII first, and then 
> sending the file without translation, then you should indeed code 
> x'0d0a'.   However, if your program is writing EBCDIC data and the 
> translation is happening later (as part of the FTP process) then you 
> should be using x'0d25'.
>
> Using the wrong code will likely result in "garbage" in the file.
>
> I strongly suspect that you should NOT be adding a CR/LF in your 
> program.  Instead, you should be letting FTP add a CRLF.  If you want 
> the records to always be exactly the same length, make sure you set the 
> TRIM option so that it doesn't trim blanks off the end of records.