|
Dave, 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 david.kahn@gbwsh.mail.abb.com on 02-25-99 11:10:31 AM Please respond to MIDRANGE-L@midrange.com To: MIDRANGE-L@midrange.com cc: (bcc: Rajan Srinivasan/Servicing/SuperiorBank) Subject: Re: FTP - To Transfer as EBCDIC Rajan.Srinivasan@Allfun.com wrote: >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.? By default the transfer will assume you want to translate from EBCDIC to ASCII. If you want to prevent this issue the EBCDIC command before the PUT, assuming the file contains text only. If the file contains characters that are not valid EBCDIC text characters (packed decimal for example) you can use the BINARY command instead. >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". As you're running the process in batch you will probably want to scan the log within your program. The " 226 Transfer complete " message is exactly what you're looking for. If you find that in the log you can assume that the PUT request was successful. I personally do not have a program to hand to share with you, but if you ask nicely you'll probably get several nice example by private e-mail from list members. Sounds as though you're making progress. Good luck. Dave Kahn, ABB Steward Ltd. +--- | 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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.