× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Jeff,

I think this post would be more appropriate in the COBOL list. Anyway, I
believe you have the right idea. The file needs to be read considering
the CCSID. Carlos Balestrazzi wrote an article on reading files in the
IFS. It's on the System i Network at:
http://www.systeminetwork.com/artarchive/newsletter/w/1001/a/54056/index.html

I don't recall if the APIs used implicitly deal with the CCSID. If you
are still puzzled, I would recommend posting this on a COBOL list or
forum.

Michael Quigley
AS/400 Programming Section
The Way International
www.TheWay.org

wdsci-l-bounces@xxxxxxxxxxxx wrote on 10/19/2007 08:59:15 AM:
date: Fri, 19 Oct 2007 09:00:33 -0400
from: Jeff Buening <JeffBuening@xxxxxxxxxxxxxxxxxxx>
subject: [WDSCI-L] XML PARSE AND XML GENERATE

Has anyone had any success using the XML PARSE and XML GENERATE commands

you can use in ILE COBOL or RPG and using the parser that is in the Xml
Toolkit? I have issues with pulling in an XML file from the IFS because

it comes in all jibberish. I get the XML PARSE to work when I just code

the XML data into the ILE COBOL program, but am missing something when
pulling in from IFS. I think it has something to do with CODE PAGE
CCSID
that I use from what I read (don't quite understand the CCSID).

Thanks,
Jeff Buening

Programmer/Analyst
jeffbuening@xxxxxxxxxxxxxxxxxxx
Phone: 419-586-8599
FAX #: 419-586-6224
www.celinainsurance.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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.