Interoperability with IBM Host Systems

Transaction and Data Access Scenarios

COMTI should be considered for the following scenarios:

Application-level database integration.
COM integration with CICS and IMS.
ADO access to legacy data.
Integration of mainframe applications that own and control the host data. Transaction programs (TPs) often contain logic and data structures that define the rules for accessing host data. In some cases, these applications also contain integrity checks and consistency constraints. In these cases, accessing the host data through these TPs is the only safe option.
Positioning of mid-tier applications to take advantage of the scalability benefits Component Services provides in addition to providing mainframe application access.
Deployment of high-integrity, distributed transaction systems that span Windows 2000, MVS/CICS, and other Extended Architecture (XA)–compliant environments that are Component Services-enabled.
Mainframe connectivity only.

OLE DB Provider should be considered for these scenarios:

Record-level or file-level database integration.
OLE DB and ADO access to legacy data.
Rewriting of business rules, such as "Year 2000" solutions.
Direct access to host data without going through the host SQL processor.
Mainframe and AS/400 connectivity.

In some cases, you might choose to use both COMTI and OLE DB Provider to develop a complete host-connectivity solution.

Sample applications that use COMTI are installed when the COMTI component is selected during SNA Server setup. For more information about using the samples, see the samples folder on the SNA Server CD.