|
I've got an application where I'm passing data to an RPG stored procedure using XML (the data is coming from a web page via Lotus Domino, but I'm not sure that's relevant). In the stored procedure, I use XML-INTO to load the data into
externally-described data structures and then store it in the associated physical files. Everything was going fine until we discovered today that some of the data contains some oddball characters -- e.g. "greater than or equal to" (U+2265). The XML
string is coming in as "≥", which looks right, but the character is not getting into the physical file correctly.
I figured it had to do with the CCSID of _something_, and my first guess was the file. I tried changing its CCSID from 37 (our default) to 65535 and also 819, but neither of them worked. I also tried 1208, but CHGPF didn't like that one. I've googled
around on the web, but a lot of what I find seems to assume that I know what CCSID I'm aiming for, but that's my problem -- I don't know how to figure out what CCSID might work.
As you can tell, I'm pretty new to all this. Am I on the right track? Should I be looking at the job's CCSID as well? At this point, I'm not sure where to begin ....
Thanks very much in advance,
Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA 01376
413-676-3144
Internal: x 444
mnaughton@xxxxxxxxxxxx
****************************************
NOTICE: This e-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that any use is
strictly prohibited. If you have received this e-mail in error, please notify us immediately by replying to it and then delete it from your computer.
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.