Rational Developer for System z
Enterprise PL/I for z/OS, Version 4.1, Programming Guide

Using the PLISAXC and PLISAXD XML parsers

Overview
The PLISAXC built-in subroutine
The PLISAXD built-in subroutine
The SAX event structure
start_of_document
version_information
encoding_declaration
standalone_declaration
document_type_declaration
end_of_document
start_of_element
attribute_name
attribute_characters
end_of_element
start_of_CDATA_section
end_of_CDATA_section
content_characters
processing_instruction
comment
namespace_declare
end_of_input
unresolved_reference
exception
Parameters to the event functions
Differences in the events
Coded character sets for XML documents
Supported code pages
Specifying the code page
Using a number
Using an alias
Exceptions
Parsing XML documents with validation
XML schema
Creating an OSR
Example with a simple document
Example of using the PLISAXC built-in subroutine
Example of using the PLISAXD built-in subroutine

The PLISAXC and PLISAXD built-in subroutines provide basic XML parsing capability, which allows programs to consume inbound XML documents, check them for well-formedness, and react to their contents.

The XML parser used by PLISAXC is non-validating, but does partially check for well-formedness errors, and generates exception events if it discovers any.

The PLISAXD built-in subroutine provides XML parsing with validation capability. It determines whether an inbound XML documentation conforms to a set of rules specified in an inbound XML schema.

The PLISAXC and PLISAXD subroutines do not provide XML generation, which must instead be accomplished by PL/I program logic or by using the XMLCHAR built-in function.

PLISAXC and PLISAXD have no special environmental requirements except that it is not supported in AMODE 24. It executes in all the principal runtime environments, including CICS, IMS, MQ Series, z/OS batch, and TSO.

Because the PLISAXC and PLISAXD built-in subroutines and the PLISAXA and PLISAXB built-in subroutines do have much similarity, some of the discussion below repeats material from the previous chapter.


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)