- ActiveX Data Objects (ADO), ADO.NET, and Object Linking and Embedding (OLE) database application interfaces
- NET Web and data services
- XML capability
- A three-tier architecture (since not all important data is on the z/OS)
- Support for multiple mainframes, multiple data types, and multiple data sources.
A Windows ’ Window into z/OS Data
There is now the capability to provide Windows 98, NT, 2000, and XP applications and browsers with real-time access to OS/390 and z/OS data, including VSAM, QSAM, IMS, and DB2 databases.
With this, an organization can receive data in real-time from a mainframe and use it in an off-the-shelf Windows or Web-enabled application, without the time-consuming, costly process of duplicating and transforming the data.
Any new or existing enterprise application can directly read data from wherever that data resides. Source data can come from any type of platform, even from multiple sources simultaneously. The data isn’t moved from its storage location; the software provides the specific data records or fields required by the requesting application, integrating data from the various sources, if necessary.
DB2 data can be merged with VSAM, QSAM, and IMS databases. By applying meta information to the unstructured mainframe files, the technology can retrieve the data as a relational structure.
For example, the end user can simply select a menu item in Microsoft Excel, request a view of mainframe data, and directly populate a worksheet. Multiple data types from multiple mainframes or Logical Partitions (LPARs) are easily joined in a single query.
Data Access Subsystem
This approach would employ a three-tier architecture:
- The data access subsystem (which operates as an authorized subsystem under OS/390)
- The data access server (Windows 2000 or NT4.0)
- The desktop (any Win 32-compatible platform).
This technology would interface at the OS level to read directly from stored data at the file or record level. The subsystem is multi-threaded; each application and file cluster is independently controlled by subsystem priority settings. This threading system enables the software to be scaled with multiple servers running on multiple threads on the mainframe, if desired.