Thanks Jon!

Actually, I might be able to use to the code to document an issue...

Charles


On Tue, Feb 28, 2017 at 4:24 PM, Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:

This is what I did for a utility program that uses XML-SAX to print out
the contents of an arbitrary XML file.

d eventCodeData DS
d 10i 0 Inz(*XML_START_DOCUMENT)
d 10i 0 Inz(*XML_VERSION_INFO)
d 10i 0 Inz(*XML_ENCODING_DECL)
d 10i 0 Inz(*XML_STANDALONE_DECL)
d 10i 0 Inz(*XML_DOCTYPE_DECL)
d 10i 0 Inz(*XML_START_ELEMENT)
d 10i 0 Inz(*XML_CHARS)
d 10i 0 Inz(*XML_PREDEF_REF)
d 10i 0 Inz(*XML_UCS2_REF)
d 10i 0 Inz(*XML_UNKNOWN_REF)
d 10i 0 Inz(*XML_END_ELEMENT)
d 10i 0 Inz(*XML_ATTR_NAME)
d 10i 0 Inz(*XML_ATTR_CHARS)
d 10i 0 Inz(*XML_ATTR_PREDEF_REF)
d 10i 0 Inz(*XML_ATTR_UCS2_REF)
d 10i 0 Inz(*XML_UNKNOWN_ATTR_REF)
d 10i 0 Inz(*XML_END_ATTR)
d 10i 0 Inz(*XML_PI_TARGET)
d 10i 0 Inz(*XML_PI_DATA)
d 10i 0 Inz(*XML_START_CDATA)
d 10i 0 Inz(*XML_CHARS)
d 10i 0 Inz(*XML_END_CDATA)
d 10i 0 Inz(*XML_COMMENT)
d 10i 0 Inz(*XML_EXCEPTION)
d 10i 0 Inz(*XML_END_DOCUMENT)

d eventCodes 10i 0 Dim(25) Overlay(eventCodeData)

d eventNameData DS
d 21a Inz('*XML_START_DOCUMENT')
d 21a Inz('*XML_VERSION_INFO')
d 21a Inz('*XML_ENCODING_DECL')
d 21a Inz('*XML_STANDALONE_DECL')
d 21a Inz('*XML_DOCTYPE_DECL')
d 21a Inz('*XML_START_ELEMENT')
d 21a Inz('*XML_CHARS')
d 21a Inz('*XML_PREDEF_REF')
d 21a Inz('*XML_UCS2_REF')
d 21a Inz('*XML_UNKNOWN_REF')
d 21a Inz('*XML_END_ELEMENT')
d 21a Inz('*XML_ATTR_NAME')
d 21a Inz('*XML_ATTR_CHARS')
d 21a Inz('*XML_ATTR_PREDEF_REF')
d 21a Inz('*XML_ATTR_UCS2_REF')
d 21a Inz('*XML_UNKNOWN_ATTR_REF')
d 21a Inz('*XML_END_ATTR')
d 21a Inz('*XML_PI_TARGET')
d 21a Inz('*XML_PI_DATA')
d 21a Inz('*XML_START_CDATA')
d 21a Inz('*XML_CHARS')
d 21a Inz('*XML_END_CDATA')
d 21a Inz('*XML_COMMENT')
d 21a Inz('*XML_EXCEPTION')
d 21a Inz('*XML_END_DOCUMENT')

d eventNames 21a Dim(25) Overlay(eventNameData)

You can find the full source for the original version of the code here if
you are interested:

http://partner400.com/examples/XMLSAXTST.htm - ignore the error on the
page.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Feb 28, 2017, at 2:40 PM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

All,

Anybody got a list of the values shown in debug for the various XML-SAX
event ID's?
*XML_START_ELEMENT
*XML_CHARS
*XML_END_ELEMENT
ect...

Named constants are nice in the source, but I need to tie those back to
the
integer values I see in debug.

Thanks!
Charles
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


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.