|
Brad, Try a table such as Q037337850 rather than QASCII. The x'BA' and x'BB' codepoints you are seeing with your EBCDIC file indicate that your file is stored in a CCSID such as 37. Your analysis of QASCII expecting x'4A' and x'5A', on the other hand, indicates that QASCII assumes you file is stored in a CCSID such as 500. By using a table such as Q037337850 you are explicitly calling for a mapping from CCSID 37 to CCSID 850 (PC Multi-lingual) and not just taking whatever the S/38 (which is where QASCII comes from) used to assume for EBCDIC and ASCII encoding. To really play it safe you could look (DSPFD) to see what CCSID the file is really in (I'm guessing 37 based on the two code points you provided) and then find the appropriate table in one of the appendixes to the International Application Development manual. Or better yet stop using tables (which like QASCII are just hold overs from previous decades) and use CCSID based interfaces. In your case, moving from I assume source files to stream files, CPY might do quite nicely. Bruce > >Working on a program that uses brackets. [ and ]. They show up as x'BA' >and x'BB' in EBCDIC. When I copy the file with them to a stream file, they >are converted to x'E2' and x'E3' for ASCII which actually is garbage and not >what I want. > >They should be x'5B' and x'5D' in ASCII. Looking at the QASCII table, the >values need to be x'4A' and x'5A' in EBCDIC do convert correctly. > >Anyone have any ideas without having to specifically specify the hex values >that will convert?? > >Brad > +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-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.