RE: FTP - To Transfer as EBCDIC

Murphy,
             Thanks . I understand from your mail that EBCDIC  might not be
supported. So, I tried your other alternative , by
sending by  BINARY, and that went smooth.
            Thanks for your info. Its so nice to get messages as quick  and
problem solving. I checked transferring the file by BINARY instead of
EBcdic, and it transfered
(  590 Total records  *  160 Total length of the file )    and it  gave
94400 bytes transfered on the Log .

Our SUN experts were checking the Transfered file and yet to receive the
status.

Thanks again

Regards
Raj






"Murphy, Guy" <murphy@uif.uillinois.edu> on 02-25-99 12:02:23 PM

Please respond to MIDRANGE-L@midrange.com

To:   "'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com>
cc:    (bcc: Rajan Srinivasan/Servicing/SuperiorBank)
Subject:  RE: FTP - To Transfer as EBCDIC




     It means that the receiving system doesn't recognize the EDCBDIC
subcomnand.  EBCDIC only works if you're sending to another 400 or to an
IBM
style mainframe.  You don't need to specify EBCDIC if you're sending to
another 400 even if you have packed or binary fields in the file,  the
default settings will work, at least at V4R3.  If you're sending the file
to
a mainframe, you should use EBCDIC to protect those packed and binary
fields.  Also EBCDIC is more efficient that BINARY or IMAGE because EBCDIC
will trim trailing blanks from the file records before sending them.
However, make sure the file you're creating on the mainframe has the same
record length as the 400 file so that it's formatting is correct.

Guy Murphy
University of Illinois
FACTS system
217-333-8670
murphyfa@uiuc.edu

-----Original Message-----
From: Rajan.Srinivasan@Allfun.com [mailto:Rajan.Srinivasan@Allfun.com]
Sent: Thursday, February 25, 1999 1:16 PM
To: MIDRANGE-L@midrange.com
Subject: RE: FTP - To Transfer as EBCDIC

Hello ,
                              Thanks for your quick response.  I tried the
sub command EBcdic , and I got a messsage
"504  Type  E  Not  Implemented".
Could you please explain me what actually this message is , and how to
solve them.
Thanks again
Raj




"Murphy, Guy" <murphy@uif.uillinois.edu> on 02-25-99 09:50:20 AM
Please respond to MIDRANGE-L@midrange.com
To:   "'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com>
cc:    (bcc: Rajan Srinivasan/Servicing/SuperiorBank)
Subject:  RE: FTP - To Transfer as EBCDIC



     The ftp default is ascii. The AS/400 assumes it's talking to an
ascii machine until told otherwise.  If you want to send the file as
ebcdic,
use the subcommand binary or image and the file will be transmitted without
converting it.
Guy Murphy
University of Illinois
FACTS system
217-333-8670
murphyfa@uiuc.edu
-----Original Message-----
From: Rajan.Srinivasan@Allfun.com [mailto:Rajan.Srinivasan@Allfun.com]
Sent: Thursday, February 25, 1999 11:31 AM
To: MIDRANGE-L@midrange.com
Subject: FTP - To Transfer as EBCDIC
Hello All,
                       This is further to my yesterdays message regarding
FTP, I tried  the solutions posted on this forum, that works great.
                        But,  When I look into the log file , at the end I
see a message saying that
" 150 ASCII DATA  CONNECTION FOR  TEST2.EBC (32.58.45.15.)"
"  226  Transfer complete "
Actually , I am tranfering from AS/400 to SUN System.
Q1. I can able to see the file on the SUN System.  But,  I would like to
send the file in EBCDIC  type.  I am not sure, the
transfered file is of  ASCII Type or  EBCDIC Type.  How to determine this.?
Q2.  Also, how to determine it has transfered the entire data?.  In the
Log, I am getting  completion message " 92424 Buytes transfered in 0.778
seconds".
Can anyone please help me on this.
Thanks in advance
Raj








+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---






+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---