The original XML is created in a variable in RPG module. This module
calls Bradley Stone's GETURI which translates it and does the HTTPS
post. The receiver variable is returned as EBCDIC. He just gave me a
patch which will support a new value in a PARM that will signal not to
translate. (Just after I coded the translate.) I know you have a HTTP
API out there but I spent $499 on a supported API call to do the HTTPS
post so I did not have to code it myself. I feel that I have received
my money's worth with the support I have receive for the three
applications I have written using the API.
There is really nothing against translating it back and forth, I have a
service program to do all of my code page translations so it is a simple
proto type. Also the servers are base 520 power 5 systems with only 500
CPW so if I can spare a couple cycles? I now need to test to see how
these little boxes handle the HTTPS.
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Wednesday, October 07, 2009 8:25 PM
To: Midrange Systems Technical Discussion
Subject: Re: XML Parsing
Why translate the data to EBCDIC to begin with? Why not keep it in it's
original (ASCII? Unicode?) format?
If that's not feasible (though, I can't understand why that would be)
then why not translate it back? What's the harm?
Chris Bipes wrote:
HELP! Ok not so loud. I have an XML request that I am posting via
GETURI library. This is a real time transaction processing
application
that is posting ACH transactions via XML. The GETURI translates the
response back to EBCDIC but the XML Parser cannot understand EBCDIC.
Short of translating the variable back to ASCII, anyone know how to
make
the XML Parser from LIBEXPAT read the EBCDIC directly?
midrange.com
