Well I did debug the XMLCGI RPG application and commented out a few lines of code that appeared to be converting the %6C to %25.

I sent it off to Tony Cairns and Alan Seiden to review to see if what I found was legitimate.

And in the end I did what Jon told me to do. I modified the source, although I don't like doing, especially when I'm not 100% sure what the code chunks intent is :-)

Once they confirm if this is a real issue or not I will feel a little more at ease recommending using XMLSERVICE with XMLCGI.

Regards,

Richard Schoen | Director of Document Management Technologies, HelpSystems
T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems
richard.schoen@xxxxxxxxxxxxxxx
www.rjssoftware.com
Visit me on: Twitter | LinkedIn

-----Original Message-----
From: Richard Schoen
Sent: Wednesday, December 16, 2015 1:24 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: XMLSERVICE and losing Wildcard from SQL LIKE

Oops. put a TRIM(LSTNAM) and it works.

Not sure if that's a DB2 feature or bug when using padded char fields.

The XMLIN data buffer in the XMLCGI RPG app does contain the EBCDIC %6C coming in, but there's a routine in XMLCGI appropriately called apaHack that is messing it up and converting it to EBCDIC %25

There's no docs on what specifically it's doing and it uses a bunch of pointer stuff.

Looks like there was some change made in XMLSERVICE V1.8.0 that does a check on 6C that might be the culprit.

Regards,

Richard Schoen | Director of Document Management Technologies, HelpSystems
T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems richard.schoen@xxxxxxxxxxxxxxx www.rjssoftware.com Visit me on: Twitter | LinkedIn


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].