|
Lo wrote: >>Of course, there are PC-related workarounds, e.g. you can force CA/400 to translate 65535 data, but for that you'll need to fix every PC, because the default is no translation. One thing I can't understand is why IBM decided to convert 65535 data to character-hexadecimal representation in the first place. Who would possibly need that?<< I have actually fixed my PC with the mentioned workaround. There are no other users of file-transfer, so this is fine for us. This way many thanks to all the people answering my question. Obviously I missed really something ;-). The question of Lo, why IBM convert 65535 data to character-hex representation is a good one. I myself must admit that I don't need that. Well, I thought of writing a short program which converts this char-hex rep. to normal text. This is not necessary now since it's get fixed but I can't understand this hex-transfer either. Thanks again Chris calling from Kassel, Germany +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@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.