Mainframe Adapter Suite

The Mainframe Adapter Suite (MAS) is a collection of eight connectors, an MAS driver component, and a Mainframe Agent. The MAS integrates the following IBM OS/390-based mainframe legacy applications with the WebSphere business integration environment:

The MAS driver component and Mainframe Agent provide a single technology interface for all of the MAS connectors. Like all of the MAS connectors, the MAS drivers must be configured to support the mainframe application you want to integrate. See Configuring driver data sources, for more on configuring data sources for the drivers.

WebSphere Business Integration Adapter for ADABAS

This adapter enables WebSphere to seamlessly integrate with ADABAS. Specifically, the data held within the ADABAS system is assessible by using standard SQL. The adapter provides direct SQL or native access to ADABAS, including support for native ADABAS transactional commands.

Table 2. Adapter specifics for ADABAS

Adapter Specifics
Release ADABAS V5.0 or later
Mainframe interface standard ADALNK
JDBC statement Essential SQL for SELECT, INSERT, UPDATE, and DELETE
Metadata source ADAWAN, ADAREP

WebSphere Business Integration Adapter for CICS

For many years, IBM CICS and IBM Transaction Server has been the dominant transaction environment for many real-time, mission-critical business applications. This adapter helps businesses leverage existing CICS investments, while preserving performance, security, stability and scalability. The Adapter for CICS enables integration of business logic embedded in CICS transactions and programs with WebSphere.

Table 3. Adapter specifics for CICS

Adapter specifics
CICS transactions written in COBOL, PL/1, ASM or C
CICS release V4.1 or later and all versions of Transaction Server
Mainframe interface standard EXCI
JDBC statement CALL
Metadata source COMMAREA copybook

WebSphere Business Integration Adapter for DB2

This adapter enables WebSphere to access DB2 systems residing on z/OS or OS/390 systems through a high-performance architecture that doesn't require DRDA(R) communication or DDF address spaces for each DB2 subsystem.

Table 4. Adapter specifics for DB2

Adapter specifics
DB2 release V4 or later
Query support Static and dynamic DB2 queries
Mainframe interface standard CAF or RRSAF
JDBC statement ANSI SQL
Metadata source DB2 SYSTEM catalog

WebSphere Business Integration Adapter for IDMS Database

The Adapter for IDMS Database provides WebSphere access to IDMS/DB databases. This adapter support for IDMS/DB should not be confused with trying to integrate with the IDMS transactional environment, called IDMS/DC. Access to IDMS databases is done through a Remote Procedure Call (RPC) in MAS. RPCs exploit the best of the Adapter Server architecture, while allowing an organization to build custom interfaces to IDMS/DB subsystems.

Table 5. Adapter specifics for IDMS/DB

Adapter Specifics
IDMS/DB support V13.0 or later
Does not require purchase of any special add-on
Mainframe interface standard Native IDMS/DB I/O
JDBC statement CALL
Metadata source None - RPC based

WebSphere Business Integration Adapter for IMS Database Manager

IMS/DB is IBM's most enduring mainframe dataase. Over time, it has evolved several high-performance features that continue to make it the database of choice for highly responsive, critical customer applications. However, its hierarchical nature and proprietary access language, DL/1, has isolated IBM/DB from many integration projects underway at companies today. The Adapter for IMS Database Manager enables this isolated customer data to participate in WebSphere integration solutions.

Table 6. Adapter specifics for IMS/DB

Adapter specifics
IMS support IMS V5 or later
Mainframe interface standard CCTL/DBCTL or IMS/ODBA
JDBC statement CALL (read/write) or SQL (read-only)
Metadata source None for RPC support
SQL uses Database Description (DBD) and Program Specification Block (PSB)

WebSphere Business Integration Adapter for IMS Transaction Server

IBM IMS/TM has been the transaction management subsystem of choice where response time is important, because of its emphasis on performance and throughput, enabled by developments such as Fast Path. The Adapter for IBM Transaction Manager aims to maintain the response time and availability profile of existing applications, while providing access to these business systems for WebSphere.

Table 7. Adapter specifics for IBM/TM

Adapter specifics
IMS transactions written in COBOL, PL/1, ASM
IMS release IMS V5 or later
Mainframe interface standard APPC or OTMA
JDBC statement CALL
Metadata source MFS (primarily the MID and MOD)

WebSphere Business Integration Adapter for Natural

Natural from Software AG is a popular 4th generation language that deploys within a CICS, Batch, or Complete environment. This adapter's integration capabilities are facilitated by a Software AG component called the Advanced Communications Interface (ACI). The Adapter for Natural provides a MAS Adapter Server-resident replacement for the ACI. This ensures that Natural programs can continue to interoperate with WebSphere with little or no modification. Adapter support for Natural programs running in the Software AG Complete environment is not available at this time.

Table 8. Adapter specifics for Natural

Adapter specifics
Language support Natural V2.2.8 or later
Mainframe interface standard Advanced Communication Interface (ACI)
JDBC statement CALL
Metadata source Natural data area

WebSphere Business Integration Adapter for VSAM

This adapter provides seamless, real-time controlled access to VSAM data for WebSphere. Because nearly all organizations have VSAM files allocated to CICS regions, the Adapter for VSAM leverages CICS to remove any lock or contention concerns involved in integration with VSAM.

Table 9. Adapter specifics for VSAM

Adapter specifics
Support for KSDS (key sequenced) VSAM files
Mainframe interface standard Native VSAM I/O
JDBC statement Essential SQL for SELECT, INSERT, UPDATE, and DELETE
Metadata source VSAM copybook

Copyright IBM Corp. 1997, 2004