RE: FTP - To Transfer as EBCDIC

> 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.
        [Tim McCarthy]  Not true at all! The default of ASCII will
result in a double translation that does really nice things to any
EBCDIC hex 25 characters you've got!!!
>   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.
        [Tim McCarthy] So does ASCII..and this "feature" can cause
unexpected results...try sending files of EDI data this way into a
stream file and those blanks that mean something at the end of a wrapped
record get hacked off. 
> 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. 
        [Tim McCarthy]  This is more a feature of how the remote FTP
server interprets and stores records but in most cases you're right.  


> 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
+---