Browse Prior Art Database

Remote access to IMS DB Data using DB2 Stored Procedures and Java ResultSet objects

IP.com Disclosure Number: IPCOM000010499D
Original Publication Date: 2002-Dec-09
Included in the Prior Art Database: 2002-Dec-09
Document File: 4 page(s) / 49K

Publishing Venue

IBM

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 37% of the total text.

Page 1 of 4

  Remote access to IMS DB Data using DB2 Stored Procedures and Java ResultSet objects

Title: Remote access to IMS DB Data using DB2 Stored Procedures and Java ResultSet objects

Disclosed is a mechanism for providing remote access to IMS DB Data by using the distributed capabilities of IBM's DB2 product in combination with enhancements to the IMS provided JDBC driver. A mechanism is described to convert IMS ResultSet objects into DB2 ResultSet objects, thus allowing the results to flow to distributed clients using the Distributed Relational Database Architecture, implemented by DB2.

Historically, direct access to IMS DB data has only been available from an application that executes on the same image of z/OS (or OS/390) where IMS itself is executing. Recently, IBM has made access available to IMS DB data in SQL from a number of environments on z/OS, including DB2, using Java. However, access from platforms other than z/OS have not been supported other than by third party products that implement the access on z/OS as well as the communication protocol to distribute the results to other platforms. This submission describes a mechanism to make access available to IMS DB data from distributed platforms by utilizing the distributed capabilities of IBM's DB2 product in combination with a mechanism to convert IMS results into DB2 results. In particular, a DB2 application on a non-z/OS platform creates a Connection to a database on z/OS. The distributed DB2 uses the underlying Distributed Relational Database Architecture (DRDA) connection to DB2 on z/OS to execute a Java DB2 Stored Procedure on z/OS and return results to the distributed application. The Java Stored Procedure on z/OS creates an IMS JDBC Connection object to access IMS DB data, indicating that the results of queries are to be converted from IMS ResultSet objects to DB2 ResultSet objects. Subsequent queries issued to an IMS Statement or PreparedStatement object cause the IMS JDBC driver to create a temporary DB2 table and load it with the results of the IMS query. This allows the results of the query to be made available to the distributed platform as normal DB2 Stored Procedure results.

To support returning result sets from a DB2 Java stored procedures on z/OS which accesses IMS DB data, it is necessary for the application to specify that DB2 ResultSet objects are needed. It is also necessary to change the implementation of the IMS JDBC driver such that, when requested, it builds a DB2 Global Temporary Table from the results of an IMS query, and uses this table to return a DB2 ResultSet.

The Signal to Create DB2 ResultSet Objects

The IMS Java library supports the creation of connections using either the java.sql.DriverManager interface or the javax.sql.DataSource interface. The signal to the IMS JDBC driver to create the DB2 table and subsequent DB2 ResultSet object when using a Java DriverManager object to create the Connection object, is the

Page 2 of 4

specification of the p...