Introduction to XML and native XML technologies on the IBM Mainframe

Transcription

1 Introduction to XML and native XML technologies on the IBM Mainframe Susann Thomas, Client Technical Professional for Software on System z Susann.Thomas@de.ibm.com

2 Notices This information was developed for products and services offered in the U.S.A. Note to U.S. Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY U.S.A. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces. 2 / 128

3 Agenda Native XML technologies on the IBM Mainframe Java for z/os XML System Services XML Toolkit for z/os XML Support for Enterprise Cobol XML Support for Enterprise PL/I XML in CICS XML in WTX, DB2 and WebSphere DataPower XI50(z) Summary and conclusion

4 XML: Why it's this way Simple (like HTML -- but not quite so simple) Strict syntax rules, to eliminate syntax errors syntax defines structure (hierarchically), and names structural parts (element names) self-describing data Extensible (unlike HTML; vocabulary is not fixed) Can create your own language of elements (aka "tags") Strict syntax ensures that such markup can be reliably processed Designed for a distributed environment (like HTML) Based on Unicode text Each XML parser must be able to parse XML encoded in Unicode Can mix different data types together (unlike HTML) Can mix one set of elements with another set: resulting data can still be reliably processed

5 XML is more then syntax analyse XML compatible browser content format structure XSL stylesheet XML document DTD or XML schema other output format e.g. PDF, printer, display, language format,... XSL(T) processor HTML document HTML compatible browser

6 XML (and related) Specifications XML Core Canonical API s JDOM JAXP DOM 1 DOM 2 DOM 3 SAX 1 SAX 2 Style XPATH XSLT XSL XML signature CSS 1 CSS 2 CSS 3 SAOP XML-RPC XML 1.0 Xpointer XML query... XMI WDDX Protocols Xlink XML names XML Schema UDDI ebxml Bizztalk XML base Infoset WSDL Web Services IFX RDF XHTLML events Xforms FinXML W3C rec W3C draft Xfragment Modularized XHTML FpML Industry std Open std MathML SMIL 1 & 2 dirxml Application areas SVG... XHTML 1.0 XHTML basic 100's more...

7 Options, options, options! XML parsing options for z/os As the need to process XML data increases, you should understand the options available for handling this data format. On z/os, a number of parsing choices are readily available. For Java the primary choice is the XML4J parser, which is available in the Java SDK, along with the corresponding XSLT processor, XSLT4J. In the non-java programming environments, there are a number of alternatives, notably: Native built-in programming-language support exists in the Enterprise COBOL and PL/I products The XML Toolkit provides an Apache Xerces-based parser called XML4C and a corresponding XSLT Processor called XSLT4C XML System Services (z/os XML) provides a new base system component (for z/os 1.7 onward) for XML parsing.

8 Options, options, options! XML parsing options for z/os These alternatives have various characteristics in terms of: Functionality Standards support Performance that should be considered when you are choosing a parser to be used for a specific situation. Also, keep in mind that often there is higher-level processing available that removes the burden of you needing to parse XML data yourself.

9 Kicking down the costs of XML We know that the cost of XML processing is high, so anything that helps reduce that cost is good news, right? With z/os V1R9 or higher, and through a PTF for V1R7 and V1R8, z/os XML System Services is now able to take advantage of the lower-cost zaaps to help reduce the cost of computing when parsing an XML document. The system does this zaap enablement under the covers when any program calls the main XML parser module, GXL1PRS (GXL4PRS), or its new C/C++ equivalent service for z/os V1R9, glxpparse(). After the parser completes its processing, the system turns off zaap enablement. IBM added support for ziips to the XML System Services (z/os XML) parser. With this support, the parser will be redirected to the lower-cost ziips when running in enclave SRB mode. With respect to DB2, processing that can be partially directed to ziips like DB2 Distributed Relational Database Architecture (DRDA) benefits by directing the full amount of the z/os XML System Services processing to the ziips. IBM added parser validation support to z/os XML System Services, and to enhance the XML Toolkit for z/os so that eligible workloads can exploit z/os XML System Services. Both of these additions will exploit the ability of the z/os XML parser to use zaaps.

10 XML Batch integration XML Input Data <...> <...>... </...> </...> <...> <...>... </...> </...> Java JAXP JDOM JAXB XML Tookit for z/os (C++) Parsing Schema validation z/os XML System Services (ASM) Parsing Schema validation Enterprise COBOL & PL/I Parsing Schema validation Business logic (Java, C++, Cobol, ) DB2 (XML or relational data) Step1: XML Parsing / Validation Step 2: Business logic Step 3: Data store

11 Agenda Native XML technologies on the IBM Mainframe Java for z/os XML System Services XML Toolkit for z/os XML Support for Enterprise Cobol XML Support for Enterprise PL/I XML in CICS XML in IMS XML in WTX, DB2 and WebSphere DataPower XI50(z) Summary and conclusion

12 Die IBM zenterprise 196 und 114 Technologie wurde für Java optimiert 70+ new instructions used by Java Register high-word facility Facilitates use of upper 32-bits of registers Interlock facility update Better Java concurrency Non-destructive operands Reduce path-length Conditional-load/store Remove expensive branches Instruction scheduler for Out-of-Order pipeline Hardware for Java New Out-Of-Order pipeline design New larger cache structure Higher clock speed (~5.2GHz) z/os Java Unique Security Enhancements IBMJCECCA provider support for AES Secure Keys RAS: Provide Enhanced ICSF Exception Handling in IBMJCECCA z/os Unique Enhancements JZOS 2.4.0

13 Java-centric processing of XML Numerous XML generation, parsing, and transformation classes are available for Java. Within z/os, all Java processing is eligible to run on zaap processors. Java classes can run under the following products: Native Java within z/os UNIX WebSphere Application Server (WAS) WebSphere Message Broker WebSphere Process Server WebSphere Enterprise Service Bus (ESB) CICS TS can host native Java applications and Enterprise Java beans IMS can host native Java applications and Enterprise Java beans WAS has the ability to parse and preserve binary XML content through Message Transmission Optimization Mechanism (MTOM) and XML-binary Optimized Packaging (XOP). Many WebSphere products have the ability to initiate SOA processing using XML-based SOAP and REST protocols. XML parsing using Java is currently distinct from other IBM XML-enabled products. Java XML does not currently employ z/os XML System Services, for example.

14 Java z/os Releases IBM 31-bit SDK for z/os, Java Technology Edition, V7.0.0 Build Level: August 27, General Availability IBM 64-bit SDK for z/os, Java Technology Edition, V7.0.0 Build Level: August 27, General Availability New! Weitere Infos zum IBM Java 7 SDK: IBM 31-bit SDK for z/os, Java Technology Edition, V6.0.1 Build Level: April 19, SDK601 FP1 IBM 31-bit SDK for z/os, Java 2 Technology Edition, V5 Build Level: June 27, 2011 IBM 64-bit SDK for z/os, Java Technology Edition, V6.0.1 Build Level: April 19, SDK601 FP1 IBM 31-bit SDK for z/os, Java Technology Edition, V6.0.0 Build Level: June 25, 2011 IBM 64-bit SDK for z/os, Java Technology Edition, V6.0.0 Build Level: June 25, 2011 IBM 64-bit SDK for z/os, Java 2 Technology Edition, V5 Build Level: June 27, 2011 IBM SDK for z/os, Java 2 Technology Edition, V1.4 Build Level: February 13, 2011 This product is no longer orderable and has been withdrawn from service, effective September 30, See

15 Java and XML JAXP (Java API for XML Processing) DOM SAX XSLT (Transformation) Pluggability Layer for further parser (Xerces, Crimson, ) JDOM JAXB (Java Architecture for XML Binding) Generation of XML out of Java objects (Marshalling) and generation of Java objects out of XML (Unmarshalling) TrAX (Transformation API for XML) extends the original JAXP mission to include XML transformations provide a vendor and implementation agnostic standard Java API for specifying and executing XML transformations. is more than just a standard interface for XSLT engines is designed to be used as a general-purpose transformation interface for XML documents. XPath (XML Path Language) is the result of an effort to provide a common syntax and semantics for functionality shared between XSLT and XPointer The primary purpose of XPath is to address parts of an XML document it also provides basic facilities for manipulation of strings, numbers and booleans Very good performance improvements concerning XML since Java V6.0

16 What is JAXB? A standard set of tools and interfaces to automatically generate Java files from XML schema (xjc) generate an XML schema from Java (schemagen) bind Java to XML at runtime, based on annotations JAXB is a framework or architecture, not an implementation. Sun / Oracle provides a reference implementation of JAXB Included in JDK

17 JAXB steps XML schema Binding Compiler XML Schema derived Classes & Interfaces XML document Application JAXB APIs Content Objects

18 The JAXB binding process XML schema bind JAXB XML XML schema schema XML mapped schema classes follows Instances Validation Instances XML document unmarshal marshal XML XML schema schema XML Java schema Objects

19 What is JZOS? A launcher for the z/os JVM A toolkit to use z/os system functions from Java

20 The JZOS launcher A better alternative to BPXBATCH Setup of Java environment Flexible parameter passing JVM standard input / output / error can be classic datasets (including spool) Automatic codepage conversion Java exit code propagation Trace facility MVS console interaction

21 JCL sample //HELLOW JOB,NOTIFY=&SYSUID,MSGLEVEL=(1,1) //JAVA EXEC JVMPRC60, // LOGLVL='+T', // JAVACLS='com.ibm.jzos.samples.PdsLister', // ARGS='//SOURCE.COBOL' //STDENV DD * CLASSPATH=/u/dnet551/jzos_samples.jar JAVA_HOME=/usr/lpp/java/J6.0 PATH="/bin:$JAVA_HOME"/bin: LIBPATH=/lib:/usr/lib:"$JAVA_HOME"/bin:"$JAVA_HOME"/bin/j9vm JZOS_JVM_OPTIONS="" export JAVA_HOME PATH LIBPATH CLASSPATH JZOS_JVM_OPTIONS

22 Important references z/os Java web site IBM SDK Java Technology Edition Version 6 Supplement JZOS Batch Launcher and Toolkit Installation and User s Guide (SA ) JZOS API Javadoc:

23 Agenda Native XML technologies on the IBM Mainframe Java for z/os XML System Services XML Toolkit for z/os XML Support for Enterprise Cobol XML Support for Enterprise PL/I XML in CICS XML in IMS XML in WTX, DB2 and WebSphere DataPower XI50(z) Summary and conclusion

24 z/os XML System Services (z/os XML) z/os introduced direct support for XML parsing with z/os XML System Services z/os XML System Services is an integral part of the z/os operating system and was designed to provide XML parsing assistance with minimal path-length There is no need to download or install any additional packages to use it. From the application perspective, z/os XML System Services is a set of callable routines that parse (or validate and parse) an XML document, rendering its contents into an intermediate format that is easily navigated. Applications can focus on business processing and rely upon z/os XML System Services to handle the intricacies of atomizing an XML document. z/os XML Systems Services does not use or provide SAX or DOM interfaces. It is a buffer-oriented interface that allows the input XML to be provided in pieces and the parsed result to be consumed in pieces. There is no limit on document size using this approach. Documents of many gigabytes can be processed.

25 z/os XML System Services While z/os XML System Services does not provide SAX or DOM interfaces, the intermediate format produced by z/os XML System Services can be used to support SAX and DOM parsers as well as non-traditional parsing requirements. A number of XML-enabled products for System z use z/os XML System Services behind the scenes to gain advantage from its high-performance and consistent parsing results. For example, COBOL and PL/I provide the option of using z/os XML System Services. DB2 PureXML support also uses z/os XML System Services for some of its XML processing. z/os XML provides the option to offload most of the XML parsing to a zaap or ziip specialty engine, when present. z/os XML supports a number of character encodings, among them UTF-8, UTF-16 (big endian), IBM-1047 and IBM-037.

26 z/os XML System Services z/os XML provides a collection of programming interfaces for callers to use: C/C++ and assembler interfaces to the z/os XML parser itself. C/C++, Java, and UNIX command line interfaces to utility functions that build binary artifacts required for validation during a parse. Assembler interfaces for user exits that give callers control over how the z/os XML parser interacts with the rest of z/os. C/C++ interfaces to a service similar to a user exit, called a StringID handler, that allows for shorthand communications between the z/os XML parser and the caller.

27 z/os XML System Services - Functions Querying XML documents Parsing XML documents / document fragments without validation and with validation Output buffer format contains the parsed data stream that results from the parse process Optimized Schema Representation (OSR) are pre-processed versions of schemas String Identifiers are a special type of output data used to represent some of the strings that the z/os XML parser encounters during a parse ( 4 byte numeric) Memory management

28 z/os XML System Services Parser functions The z/os XML parser API contains 5 entry points for each addressing mode (amode) type (31 or 64-bit): GXL1CTL (GXL4CTL) - perform a parser control operation GXL1INI (GXL4INI) - initialize a parse instance GXL1PRS (GXL4PRS) - parse an input stream GXL1QXD (GXL4QXD) - query an XML document GXL1TRM (GXL4TRM) - terminate a parse instance Specify the control block address for calling these functions (e. g. native call in Cobol) Requirements: z/os XML System Services called in TCB mode 100% of z/os XML System Services parsing eligible for zaap z/os V1.9 and later z/os V1.8 + OA20308 (zaap Support) z/os V1.7 + w/ OA16303 (z/os XML System Services Rollback) + OA20308 (zaap Support)

29 z/os XML System Services Buffer-Spanning and Record Splitting Optimized Schema Representations (for validating parses only Output- Buffer 1 XML Input- Buffer 1 Input- Buffer 2 z/os XML System Services Output- Buffer 2 Output- Buffer 3 Input- Buffer 3 Output- Buffer 4 Output- Buffer 5

30 Buffers usages and flow in XML System Services Every initialization has been done and the parse can takeplace For the moment, assume that validation is not required. On the left side a XML string is provided to the parse. In this example, assume that the complete document is too large to be read into a single buffer. The reader function of the application fills a buffer and advances this as parsing progresses. Logically, the reader slides a buffer window over the XML string. The address of the position of the window is passed to z/os XML System Services routine gxlprs(), which is the parsing routine. A lso passed to gxlprs() is the address of an output buffer where the results are stored.

31 z/os XML System Services parsed data stream The parsed XML data stream contains unique record type identifiers for the different components within an XML document. Among the record types are: XML declaration, when present Start of an element Character value for an element, when present End of an element Name of an attribute Value of an attribute Namespace declaration

32 z/os V1.12 validating parser performance improvements over z/os V1.11.

33 XML4C 5.7 numbers for (non)-validating parsing (compared to z/os XML System Services V1.11 and V1.12.)

34 Agenda Native XML technologies on the IBM Mainframe Java for z/os XML System Services XML Toolkit for z/os XML Support for Enterprise Cobol XML Support for Enterprise PL/I XML in CICS XML in IMS XML in WTX, DB2 and WebSphere DataPower XI50(z) Summary and conclusion

35 XML Toolkit for z/os Cross-platform, open-source code based Parser (C++) for z/os Unix Environment (UNIX shell or BPXBATCH) or MVS Environment (TSO or batch) DOM SAX XML XML Namespace XML Schemata XML Transformation XPath Release Toolkit Components and Apache Equivalents V1.3 V1.4 V1.5 V1.6 V1.7 V1.8 V1.9 V1.10 XML4C (XML Parser, C++ Edition) Comparable Xerces C XSLT4C (XSLT Processor, C++ Edition) N/A Comparable Xalan C N/A

36 XML Toolkit for z/os Latest Update The XML Toolkit can now use z/os XML System Services. This improvement provides z/os optimized C++ classes that allow eligible XML Toolkit processing zaap Support Improved performance Note: Optional usage of z/os XML by XML Parser, C++ Edition users for (non)-validating parsing is also available in XML Toolkit V1.9 by using PTFs UA40707 and UA40708 Requirements: IBM XML Toolkit for z/os, V bit support: PTFs UA51089, UA51090, and UA51091 IBM XML Toolkit for z/os V1.9 PTFs UA40707 and UA40708

37 XML Toolkit for z/os architecture XML XML Toolkit for z/os XSLT processor XML Text HTML XSLT XML Toolkit parser z/os XML System Services XML C++ SAX application XML Toolkit parser z/os XML System Services XML C++ DOM application XML Toolkit parser z/os XML System Services

38 Flow of parsing with existing XML Toolkit C++ parsers

39 Flow of parsing with existing XML Toolkit C++ parsers and z/os-specific parsers

40 XML Toolkit for z/os with XMLSS usage - Code example #include <xercesc/zparsers/zxmlrea derfactory.hpp>... SAX2XMLReader* parser = zxmlreaderfactory::createx MLReader(); #include <xercesc/sax2/sax2xmlreader.hpp> #include <xercesc/zparsers/zxmlreaderfactory.hpp> #include <xercesc/sax2/defaulthandler.hpp> #include <xercesc/util/xmlstring.hpp> #if defined(xerces_new_iostreams) #include <iostream> #else #include <iostream.h> #endif XERCES_CPP_NAMESPACE_USE int main (int argc, char* args[]) { try {XMLPlatformUtils::Initialize();} catch (const XMLException& tocatch) { char* message = XMLString::transcode(toCatch.getMessage()); cout << "Error during initialization! :\n"; cout << "Exception message is: \n" << message << "\n"; XMLString::release(&message); return 1;} char* xmlfile = "x1.xml"; SAX2XMLReader* parser = zxmlreaderfactory::createxmlreader(); parser->setfeature(xmluni::fgsax2corevalidation, false); parser->setfeature(xmluni::fgsax2corenamespaces, true); DefaultHandler* defaulthandler = new DefaultHandler(); parser->setcontenthandler(defaulthandler); parser->seterrorhandler(defaulthandler); try {parser->parse(xmlfile);} catch (const XMLException& tocatch) { char* message = XMLString::transcode(toCatch.getMessage()); cout << "Exception message is: \n" << message << "\n"; XMLString::release(&message); return -1;} catch (const SAXParseException& tocatch) { char* message = XMLString::transcode(toCatch.getMessage()); cout << "Exception message is: \n" << message << "\n"; XMLString::release(&message); return -1;} catch (...) { cout << "Unexpected Exception \n" ; return -1;} delete parser; delete defaulthandler; return 0; }

41 Performance Highlights The results were generated by measuring performance when parsing a set of XML documents of various sizes and complexities. The number of CPU cycles required to parse a single byte was determined by calculating the geometric mean of the per byte costs for all benchmark documents. Significant raw performance improvement can be achieved for non-validating parsing. The performance of the validating parser depend greatly on size and complexity of the schema and the document being parsed. The following chart shows the performance boost from using z/os XML System Services for non-validation parsing.

42 General performance recommendations for XML Parser components Use DTD and schema grammar caching to reduce the cost of validation Turn validation off when not needed and avoid DOCTYPE clauses Use special scanner when document validation type is known (default document scanner IGXMLScanner; special scanners are WFXMLScanner for well-formedness checking only, DGXMLScanner for DTD validation only, and SGXMLScanner for schema validation only ) For best validating performance, use a DTD instead of a schema Use external entities and external DTD's only when necessary (extra file opens and the transcoding setup they require is expensive) Avoid multiple parses of the same document (f.e. storing the results of the initial parse in a format which may be efficiently accessed at a later time)

43 General performance recommendations for XML Parser components Reuse the initialized parser Avoid unnecessary document conversions Reduce character count Pre-normalize line end characters (two character sequence x'0d0a' and any occurrence of a solitary x'0d' with the single character x'0a' ) Avoid using default attributes If possible, use SAX instead of DOM, especially when parsing large documents Store your XML documents in the z/os or OS/390 UNIX HFS

44 XML Parser, C++ Edition performance recommendations If your applications are compiled with the XPLINK option, use the XPLINK version of the XML4C parser. Use the new DOM bindings Disable namespace support if not needed Be careful when using getelementsbytagname("*").getlength() This method walks the entire DOM tree to count the number of elements. If your DOM is large, this can be expensive Pass fully qualified pathnames Optimize your Language Environment parameters The important parameters to specify are HEAPP(ON), LIBS(1K,1K,Keep), and STOR(,,,8). You may also need to override the sizes of HEAPS and STACKS if more storage is required. Follow z/os and OS/390 UNIX, C/C++, and Language Environment guidelines

45 XSLT processor, C++ Edition performance recommendations Compile the stylesheet once and then reuse it Check heap and heap pool usage and adjust settings if necessary Use the Language Environment HEAPPOOLS(ON) and RPTSTG(ON) run-time options to check heap and heap pool usage.

46 Agenda Native XML technologies on the IBM Mainframe Java for z/os XML System Services XML Toolkit for z/os XML Support for Enterprise Cobol XML Support for Enterprise PL/I XML in CICS XML in IMS XML in WTX, DB2 and WebSphere DataPower XI50(z) Summary and conclusion

47 COBOL and z/os XML System Services combinations Note: You also can call the glue code of the XML Toolkit for z/os XSLT Processor C++ Edition / XML Toolkit for z/os Parser C++ Edition from COBOL directly.

48 Enterprise COBOL XML support Inbound XML parsing and outbound XML generation: XML PARSE xml-doc PROCESSING PROCEDURE xml-handler XML GENERATE xml-doc FROM data-item COUNT IN char-count XML parsing: Runs in all COBOL run-time environments: CICS, IMS, batch, TSO, USS, Works with any transport mechanism for XML documents Use MQSeries, CICS transient queue or COMMAREA, IMS message processing queue, WebSphere, etc. Provides basic SAX-style parsing Checks well-formedness and since COBOL V4.2 validity XML Parser is part of the COBOL run-time library XML generation: Single statement transforms entire data structure (group)

49 Enterprise COBOL XML support New compiler option: XMLPARSE(COMPAT XMLSS) COMPAT use existing XML parser (built in to COBOL library) XMLSS use new z/os XML System Services parser Improved support for parsing XML documents that use XML namespaces Direct support is provided for parsing XML documents that are encoded in UTF-8 Unicode Support for parsing very large XML documents, a buffer at a time More control of output XML document: XML documents now can be encoded in UTF-8, as well as UTF-16 Unicode or various EBCDIC codepages

50 Parsing XML using IBM Enterprise COBOL IBM Enterprise COBOL has support for XML Parsing (XML PARSE) Generation (XML GENERATE) Parser based on event model of parsing Java gurus: Same concept as SAX parsing Document can be processed in 'segments' (no longer needs to be in working storage completely) Optionally, documents can be validated (using XMLSS and compiled schemas)

51 Example: Using the XML PARSE verb 01 MY-DOCUMENT PIC N(1024) NATIONAL. PARSE-XML SECTION. XML PARSE MY-DOCUMENT PROCESSING PROCEDURE XMLEVENT-HANDLER ON EXCEPTION DISPLAY 'XML DOCUMENT ERROR ' XML-CODE NOT ON EXCEPTION DISPLAY 'XML DOCUMENT SUCCESSFULLY PARSED.' END-XML.

52 Example: Using the XML PARSE verb 01 MY-DOCUMENT PIC N(1024) NATIONAL. PARSE-XML SECTION. XML PARSE MY-DOCUMENT PROCESSING PROCEDURE XMLEVENT-HANDLER ON EXCEPTION DISPLAY 'XML DOCUMENT ERROR ' XML-CODE NOT ON EXCEPTION DISPLAY 'XML DOCUMENT SUCCESSFULLY PARSED.' END-XML. XMLHANDLERS SECTION. XMLEVENT-HANDLER. EVALUATE XML-EVENT WHEN 'START-OF-ELEMENT'... WHEN 'CONTENT-CHARACTERS'... END-EVALUATE.

53 XML event handler Called by COBOL runtime during parsing ( callback ) Special register XML-EVENT contains type of event : Begin / end of document Begin / end of an element Start of text Special register XML-TEXT or XML-NTEXT contains event-related information

54 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich>

55 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: START-OF-DOCUMENT XML-NTEXT: (entire document)

56 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: VERSION-INFORMATION XML-NTEXT: 1.0

57 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: VERSION-INFORMATION XML-NTEXT: ibm-1140

58 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: COMMENT XML-NTEXT: <!--This document is just an example-->

59 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: START-OF-ELEMENT XML-NTEXT: sandwich

60 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: START-OF-ELEMENT XML-NTEXT: bread

61 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: ATTRIBUTE-NAME XML-NTEXT: type

62 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: ATTRIBUTE-CHARACTERS XML-NTEXT: baker

63 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: ATTRIBUTE-CHARACTERS XML-NTEXT:

64 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: ATTRIBUTE-CHARACTERS XML-NTEXT: s best

65 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: END-OF-ELEMENT XML-NTEXT: bread

66 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: END-OF-ELEMENT XML-NTEXT: bread

67 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: PROCESSING-INSTRUCTION-TARGET XML-NTEXT: spread

68 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: PROCESSING-INSTRUCTION-DATA XML-NTEXT: please use real mayonnaise

69 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: START-OF-ELEMENT XML-NTEXT: meat

70 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: CONTENT-CHARACTERS XML-NTEXT: HAM

71 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: CONTENT-CHARACTERS XML-NTEXT: &

72 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: CONTENT-CHARACTERS XML-NTEXT: turkey

73 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: END-OF-ELEMENT XML-NTEXT: meat

74 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: START-OF-ELEMENT XML-NTEXT: filling

75 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: CONTENT-CHARACTERS XML-NTEXT: Cheese, lettuce, tomato, etc.

76 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: END-OF-ELEMENT XML-NTEXT: filling

77 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: START-OF-CDATA-SECTION XML-NTEXT: <![CDATA[

78 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: CONTENT-CHARACTERS XML-NTEXT: We should add a <relish> element in future!

79 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: START-OF-CDATA-SECTION XML-NTEXT: ]]>

80 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: END-OF-ELEMENT XML-NTEXT: sandwich

81 Example: XML-EVENTs and XML-NTEXT <?xml version= 1.0 encoding= ibm-1140?> <!--This document is just an example--> <sandwich> <bread type= baker&apos;s best /> <?spread please use real mayonnaise?> <meat>ham & turkey</meat> <filling>cheese, lettuce, tomato, etc.</filling> <![CDATA[We should add a <relish> element in future!]]> </sandwich> XML-EVENT: END-OF-DOCUMENT XML-NTEXT: (empty)

82 New in Enterprise COBOL V4R2 XML PARSE with validation In Enterprise COBOL, a schema used for XML validation must be in a preprocessed format known as Optimized Schema Representation, or OSR. To generate a schema in OSR format from a text-form schema, use the z/os UNIX command xsdosrg, which invokes the OSR generator provided by z/os XML System Services. Example: to convert the text-form schema in file item.xsd to a schema in preprocessed format in file item.osr, you can use the following z/os UNIX command: xsdosrg -v -o /u/hlq/xml/item.osr /u/hlq/xml/item.xsd Use one of two forms of the VALIDATING phrase, depending on the location of the preprocessed schema: In one form, you use the FILE keyword and specify an XML schema name. In this case, the schema must be in an MVS data set or a z/os UNIX file. In the other form, you specify the identifier of a data item that contains the schema.

83 New in Enterprise COBOL V4R2 XML PARSE with validation XML PARSE xmldoc VALIDATING WITH FILE myschema PROCESSING PROCEDURE p1 END-XML If you use the FILE keyword and specify an XML schema name, the COBOL runtime library automatically retrieves the schema during execution of the XML PARSE statement.

84 New in Enterprise COBOL V4R2 XML PARSE with validation To associate an XML schema name with the external file that contains the schema, code the XML-SCHEMA clause in the SPECIAL-NAMES paragraph, specifying either a literal or a user-defined word to identify the file. For example, you can associate the XML schema name myschema with the ddname DDSCHEMA by coding the ddname as a literal in the XML-SCHEMA clause as follows: ENVIRONMENT DIVISION. CONFIGURATION SECTION. SPECIAL-NAMES. XML-SCHEMA myschema IS 'DDSCHEMA'. For running the program, you can associate ddname DDSCHEMA with the z/os UNIX file item.osr by coding a DD statement as follows: //GO.DDSCHEMA DD PATH='/u/HLQ/xml/item.osr Or you can use an analogous TSO ALLOCATE command. Alternatively, DDSCHEMA could be the name of an environment variable that identifies the external file by means of a DSN option that specifies an MVS data set or a PATH option that specifies a z/os UNIX file

85 New in Enterprise COBOL V4R2 XML PARSE with validation XML PARSE xmldoc VALIDATING WITH myschema-id PROCESSING PROCEDURE p1 END-XML If you do not use the FILE keyword and specify an XML schema identifier, the schema must be in the specified data item during execution of the XML PARSE statement. VParse section. Perform Get-schema Display "Completed reading schema into memory" Perform Validate-XML Display "Completed validating PARSE" If document-valid Perform Process-data-from-XML End-if.

86 New in Enterprise COBOL V4R2 XML PARSE with validation Data division. File section. FD F2 block contains 0 recording mode is F. 01 R2 Pic x(80). Local-storage section. 01 fs2 Pic DOCL Pic 9(9) BINARY. 01 myschema-id Pic X( ).

87 New in Enterprise COBOL V4R2 XML PARSE with validation Get-schema section. Open input F2 If FS2 not = 0 then Display 'OPEN failed,' 'FS=' FS2 Goback End-if Set Not-EOF To TRUE Compute DocL = 1 Perform Until EOF Read F2 At End Set EOF To TRUE Display "EOF on F2" Not At End Display "Read: " R2(1:80) Move R2(1:80) To myschema-id(docl:80) Add 80 To DocL End-If End-Read End-Perform Close F2.

88 New in Enterprise COBOL V4R2 XML PARSE with validation Validate-XML section. Display "Reading and parsing XML..." Open input F1 Read F1 Display "Read: " R1(1:L) XML parse R1(1:L) VALIDATING WITH myschema-id with encoding 1047 processing procedure P End-XML Close F1.

89 New in Enterprise COBOL V4R2 XML PARSE with validation VALIDATING WITH identifier Requires schema in memory before XML PARSE statement Use COBOL READ, EXEC CICS READ or SQL SELECT to get schema into memory Supported under CICS Could be efficient to read the schema into memory once and reuse it for subsequent XML documents VALIDATING WITH FILE Reads schema into memory for every parse: convenient, but slow Not supported under CICS

90 New in Enterprise COBOL V4R2 Performance improvements to parsing XML documents without validation In Enterprise COBOL V4R1, some users found that XML PARSE was slow with XMLPARSE(XMLSS) Typical setup was STORAGE(00) ANYHEAP(FREE) Solution STORAGE(NONE) or ANYHEAP(KEEP) In Enterprise COBOL V4R2 this problem is solved You get the better performance with any settings

91 Agenda Native XML technologies on the IBM Mainframe Java for z/os XML System Services XML Toolkit for z/os XML Support for Enterprise Cobol XML Support for Enterprise PL/I XML in CICS XML in IMS XML in WTX, DB2 and WebSphere DataPower XI50(z) Summary and conclusion

92 XML Support in Enterprise PL/I Parsing of XML: PLISAXA(e, p, x, n, c) V3.1 PLISAXB(e, p, x, c) V3.1 PLISAXC(e, p, x, n, c) V3.8 PLISAXD(e, p, x, n, o, c) V4.1 Generation of XML: XMLCHAR e p x n o c Event structure Pointer value / token Address of buffer, or input filename (for PLISAXB) Number of bytes in buffer Address of buffer containing OSR Codepage of XML document (optional)

93 XML Parsing: PLISAXA, PLISAXB, PLISAXC, PLISAXD Input Validating Namespaces Pull z/os XML PLISAXA PLISAXB PLISAXC PLISAXD

94 XML Events (Selection) Name of the Event start_of_document end_of_document start_of_element end_of_element attribute_name attribute_characters content_characters end_of_input exception Meaning Start of the document End of the document Start of an element (start tag) End of an element (end tag) Name of the attribute Value of the attribute Content End of the input buffer is reached error occurred

95 Event declaration dcl 1 eventhandler static, 2 e01 type event_without_data init( start_of_document ), 2 e02 type event init( version_information ), 2 e03 type event init( encoding_declaration ), 2 e04 type event init( standalone_declaration ), 2 e05 type event init( document_type_declaration ), 2 e06 type event_without_data init( end_of_document ), 2 e07 type event_with_namespace init( start_of_element ), 2 e11 type event_without_data init( start_of_cdata ), 2 e12 type event_without_data init( end_of_cdata ), 2 e13 type event_with_flag init( content_characters ), 2 e14 type event_pi init( processing_instruction ), 2 e15 type event init( comment ), 2 e16 type event_namespace_dcl init( namespace_declare ), 2 e17 type event_end_of_input init( end_of_input ), 2 e18 type event init( unresolved_reference ), 2 e19 type event_exception init( exception ) ;

96 Event handler start_of_element: proc( usertoken, xmltoken, TokenLength, nsprefix, nsprefixlength, nsuri, nsurilength ) returns( byvalue fixed bin(31) ) options( byvalue linkage(optlink) ); dcl usertoken pointer; dcl xmltoken pointer; dcl tokenlength fixed bin(31); dcl nsprefix pointer; dcl nsprefixlength fixed bin(31); dcl nsuri pointer; dcl nsurilength fixed bin(31); put skip list( lowercase( procname() ) ' <' substr(xmltoken->chars,1,tokenlength ) '>' ); return(0); end;

97 Parser Call dcl token char(8); dcl xmldocument char(4000) var; xmldocument = '<?xml version="1.0" standalone="yes"?> '<!--This document is just an example-->' '<sandwich>'... '</sandwich>' ' '; call plisaxc( eventhandler, addr(token), addrdata(xmldocument), length(xmldocument) );

98 Parsing XML documents with validation PLISAXD not only parses XML documents in the same manner as PLISAXC, but also determines whether an inbound XML document conforms to a set of rules specified in an inbound XML schema. The inbound schema used for XML validation must be in a preprocessed format known as an Optimized Schema Representation (OSR). To generate a schema in the OSR format from a text-form schema, use the z/os UNIX command xsdosrg, which invokes the OSR generator provided by z/os XML System Services. xsdosrg -v -o /u/hlq/xml/stock.osr /u/hlq/xml/stock.xsd cp -p /u/hlq/xml/stock.osr "//'HLQ.XML.OSR(STOCK)'" PLISAXD requires the XML schema file to be read into a buffer

99 Generating XML with XMLCHAR XMLCHAR (x, p, n) x Structure reference p Address of target buffer n Length of target buffer Dumps data from a structure as XML into a buffer Returns the number of bytes written to the buffer If buffer too small, data is truncated and number of bytes needed is returned Each name in the structure will be written out, enclosed as start / end tags Numeric and bit data will be converted to character Leading and trailing blanks will be trimmed wherever possible

100 XMLCHAR restrictions Structure must contain only computational data (string and numeric) Structure may contain arrays, but if itself is an array, then it must be completely subscripted Structure may contain substructures, but any contained substructure must not use an * in place of a name However, an * may be used as the name of a base element, but in that case, the unnamed element will not be written to the target buffer No attributes No namespace support No generation of XML declaration No user-specified encoding (use MEMCONVERT built-in function)

101 Agenda Native XML technologies on the IBM Mainframe Java for z/os XML System Services XML Toolkit for z/os XML Support for Enterprise Cobol XML Support for Enterprise PL/I XML in CICS XML in WTX, DB2 and WebSphere DataPower XI50(z) Summary and conclusion

102 z/os XML Requirements Workload z/os XML System Services, non-validating parsing, executing in TCB mode Examples - any SW using z/os XML System Services parsing in TCB - EXAMPLE : local applications inserting/ saving XML data, and XML table loads on DB2 9 Available Sept, 2007 (with z/os V1.9 GA) Redirect 100% of z/os XML System Services parsing - eligible for zaap Requirements DB2 9 New Function Mode z/os 1.9 z/os 1.8 (with OA20308) z/os 1.7 (1) (w/ OA16303 and OA20308) - select XML Toolkit for z/os V1.9 parsing workloads May, 2008 same XML Toolkit for z/os V1.10 or V1.9 (5655-J51) with PTFs UA40707 and UA40708 C API for z/os XML System Services available with z/os 1.9, and z/os 1.7 & 1.8 with APAR OA18713 z/os XML System Services, non-validating parsing, executing in enclave SRB mode - Enterprise COBOL V4.1, using XMLPARSE option - DB2 9 inserting/ saving XML data using DRDA via TCP/IP Dec, 2007 (with COBOL V4.1 GA) Sept (with GA of z/os V1.8) same Same % as the ziipeligible work (DRDA) Enterprise COBOL V4.1 (5655-J51) z/os V1.7 (1) - V1.9 with OA22777 (SW Announce ). DB2 9 New Function Mode z/os 1.8, z/os 1.7 (1) w/ OA any SW (including DB2 9) using z/os XML System Services in enclave SRB mode GA of z/os V % of z/os XML System Services parsing eligible for ziip z/os 1.9 and 1.8 (both with APAR OA22035) DB2 9 NFM z/os XML System Services with validating parsing, both enclave SRB and TCB modes. - any SW using z/os XML System Services validating parsing GA z/os V % of z/os XML System Services validating parsing eligible for zaap (TCB) or ziip (enclave SRB) z/os V1.10 and 1.9 (with APAR OA25903) - select XML Toolkit for z/os workloads Nov same XML Toolkit for z/os V1.10 Java-based XML parsing - applications using Java-based XML parser in IBM SDK - any SW performing XML parsing/ processing in Java Yes (with availability of zaap) 100% of Java-based XML parsing eligible for zaap Any z/os, System z processor with zaap support.