Re: FTP to AS400 from Unix server gives Hex 0D at end

Scott,

it is being sent to a PF, and I am suspecting that the 0d was already in the
Unix file, which was due to botch up from transferring from Windows server.
I did not know they were doing that transfer from Windows to Unix, I just
found it out. When transferring from Windows to Unix, what is the default?
Do you have to specify ASCII transfer explicitly?

I have all these theories, ready to be investigated, but the person sending
from the Unix server is still "absconding". So I can't try anything new. :-(

On Thu, Mar 4, 2010 at 4:49 PM, Scott Klement
<midrange-l@xxxxxxxxxxxxxxxx>wrote:

Hi Vinay,

Are you FTPing to a PF or a STMF?

What you describe is the standard behavior when sending data in ASCII
mode to a STMF -- but I don't know why this would happen if you're
sending to a PF, unless the hex 0d was already in the Unix file (which
would be unusual on Unix -- but maybe it got transferred from a Windows
computer earlier without proper conversion)


On 3/4/2010 10:53 AM, Vinay Gavankar wrote:

Hi All,

One of our partners is FTPing data from a Unix FTP server to the AS400. I
get a Hex '0D' at the end.

When the data being sent was matching in length (AS400 file record length
was 368 characters and partner claimed that he was sending 368

characters),

the last character (which was a blank) was replaced by X'0D'. When he

sent

another file with varying data lengths (to a different AS400 file), on

the

AS400 I get the X'0D' was after the last character, followed by blanks.

I tried googling, and even though got a few hits with the same problem,

did

not find any solution.

TIA for any suggestions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.