|
What is the hex value for what you see as dollar sign in a source file? I would be suspicious here because hex code for dollar sign in UK code page is different from US. What you see on a screen is a combination of a file code page, job code page and device character set (if you are looking from PC then another layer is involved). You should be careful that all is done in sync - e.g. if you are looking at UK system, then UK system should be configured for UK code page and your PC should be configured for UK character set. Bottom line - look at the hex value in a file and check against a code page table: http://www-1.ibm.com/servers/eserver/iseries/software/globalization/codepages.html Alexei Pytel always speaking for myself David Gibbs <david@midrange.co To: midrange-l@midrange.com m> cc: Sent by: Subject: RE: CPYTOSTMF character translation redux midrange-l-admin@m idrange.com 12/07/2002 08:37 AM Please respond to midrange-l At 07:56 PM 12/6/2002, you wrote: >It isn't clear what you mean by "translated incorrectly". Do you mean the >hex value is incorrect or that it displays incorrectly? A dollar sign typed into the source pf shows up as something other than a dollar sign in the stream file. >In particular, is the hex representation of the "$" (US dollar sign) >correct when the file is viewed in hex? If it is, then I'd look at the >character set being used by whatever device is doing the display. To be honest, I haven't looked at the hex representation of the characters ... I really don't expect any weird translation to occur, as a dollar sign is part of both the basic ascii & ebcdic character set. The source pf is a standard ccsid 37, and the stream file code page is *PCASCII ... that translation does not seem like it should be rocket science to me. david _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.