IBM Systems Magazine, Mainframe - September/October 2010 - (Page 50)

Developer System z application development Storing and Processing XML in DB2 W\YL?43ÃL_[LUKZÃ H]HPSHIPSP[`ÃHUKÃ ZJHSHIPSP[`Ã[VÃ +)%ÃMVYÃa"6: BY T RO Y COL EM AN ; he idea of storing XML data in DB2* has been around for awhile. The first support was introduced through XML extenders in DB2 Universal Database (UDB) for Linux*, UNIX* and Windows* version 5.0 in 1999. DB2 UDB for z/OS* version 7 introduced the large object (LOB) data type, which provided a way to store an XML document, but wasn’t a viable solution due to the overhead of converting character data to LOB and then LOB back to character. Editor’s Note: This is the third installment of a continuing series on XML, DB2 and COBOL development on the z/OS platform. Previously published articles are available online: “Process XML Documents Within COBOL and DB2” The introduction of XML extenders in DB2 UDB for z/OS version 8 provided a method for developers to access the XML nodes within a document, however the performance issues associated with converting to and from LOB continue to be a problem. Due to performance and scalability issues, most companies delay XML application development with DB2 for z/OS. The concerns for performance and scalability are no longer valid with DB2 9 for z/OS. With this release, relational data is stored in relational format, and XML data is stored in native XML format using a new hybrid database engine. The database engine has integrated pureXML technology that not only provides an unprecedented level of performance, but also offers the availability and scalability for XML data you’ve come to expect when processing relational data. pureXML is designed to remove the complexities of trying to store XML data in LOB data types. XML data retrieval has also greatly improved. Since data doesn’t have to be converted from LOB to character and you can index into the XML document, the optimizer can choose an efficient access method for data retrieval. With a single SQL statement you can retrieve both relational and XML data. The DB2 optimizer can use indexes defined on both relational and XML data to determine the most efficient access path. Unlike XML data stored hÁ mainframe/septemberoctober09/ administrator/26607p1.aspx and “COBOL and XML Parsers” hÁ mainframe/processing_XML_ documents/32657p1.aspx 50 SEPTEMBER /OCTOBER 2010

Table of Contents for the Digital Edition of IBM Systems Magazine, Mainframe - September/October 2010

IBM Systems Magazine, Mainframe - September/October 2010
Editor's Desk:  Not So Secret Sauce
Dashboard:  Find an Extra Day
Think Smarter:  Competing Takes Equal Parts Growth and Restraint
Data Display:  Privacy:  Who Do You Trust?
Insider:  Untangling the Web of Processes and Technology
Trends:  System z as the Hub of a Workload-Optimized, Business Analytics Systems
Case Study: A Merger Made Easy" EmblemHealth Saves Money By Easing into an In-Sourced Computing Model
Expanding Beyond Borders:  IBM zEnterprise Systems Announcement Delivers a New Dimension in Computing.
Reducing Complexity:  The Next-Generation System z Server Is More Than Just a Fast, Scalable Solution
Focus on Storage:  IBM Tivoli Key Lifecycle Manager Solves Security Problems and Meets New Standards
Administrator:  z/OS Management Facility V1.12 Includes New Workload-Management and Resource-Monitoring Functionality
Developer: pureXML Extends Availability and Scalability to DB2 for z/OS
Advertisers' Index
Stop Run:  IBM Cooling Expert Roger Schmidt Says the Positioning of Machines Matters
2011 Mainframe Buyer's Guide

IBM Systems Magazine, Mainframe - September/October 2010