|
At 09:05 AM 6/9/98 -0700, you wrote: >John, > >One word of caution - I think there is a problem with the IBM-supplied >QASCII translation table with regard to the CR character. It has to end >up as hex 0D in ASCII, but I think doesn't do this the way you would >expect. You might need to use your own table. Let me know if you would >like some source for an EBCDIC to ASCII translation table. I'm reaching >back in my memory (which is unreliable at best), but I think I used >EBCDIC hex 25 instead of 15. > Actually it's the line feed character you need to watch for because QASCII and QEBCDIC are not reversable. Ascii x'0A' = Ebcdic x'15' but not the other way around, you have to use x'25'. You should change the translation table not the data (if you're working in C) 'cause AS/400 C functions like 'gets' will only recogize x'15' as newline. +--- | 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-2024 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.