Communication Models

Transaction Integrator (TI) supports the following communication protocols for interacting with the host computer. These protocols are limited to single request/single response. However, the request and response can consist of multiple data segments in the case of unbounded recordsets.

  • CICS TCP Transaction Request Message Link
    The host transaction must be IBM DPL-enabled. In other words, the mainframe transaction must be designed to be invoked by EXEC CICS LINK.
  • CICS TCP Transaction Request Message User Data
    The host transaction must use explicit TCP SEND/RECEIVE.
  • CICS LU 6.2 Link
    The host transaction must be IBM DPL-enabled (Distributed Program Link), that is, the mainframe transaction must be designed to be invoked by EXEC CICS LINK.
  • CICS LU 6.2 User Data
    The host transaction must use explicit APPC SEND/RECEIVE.
  • IMS Connect
    Enables you to use TCP/IP with your IMS-based TP without recompiling it. By using IMS Connect or OTMA, you can connect to existing IMS transactions without linking listeners to the TPs.
  • IMS Implicit
    The IMS program must use implicit message queue and IMS library CBLADLI (rather than CBLTDLI).
  • IMS Explicit
    The host transaction must use explicit TCP SEND/RECEIVE.
  • IMS LU 6.2 User Data
    The IMS program must use an implicit message queue (the common design model).
  • OS/400 Distributed Program Calls

See Also

Planning for Transaction Integrator

To download updated Host Integration Server 2004 Help from www.microsoft.com, go to http://go.microsoft.com/fwlink/?linkid=29507.

Copyright © 2004 Microsoft Corporation.
All rights reserved.
Show: