Overview of CICS System/390-non-System/390 intercommunication

Note

In this chapter and throughout this book, the generic term CICS® on System/390® represents all CICS System/390 products.

Interproduct communication between System/390 and non-System/390 CICS systems uses the Systems Network Architecture (SNA) LU 6.2 protocol. The descriptions in this chapter assume LU 6.2 links.

Below is a list of the supported facilities. Every CICS on System/390 product supports all these facilities.

Function shipping (see Function shipping)
File control, temporary storage, transient data, syncpoint, and interval control requests can be shipped in either direction between System/390 and non-System/390 CICS systems.
Transaction routing (see Transaction routing )
Transactions can be routed over an LU 6.2 link in either direction between System/390 and non-System/390 CICS systems.
Distributed program link (DPL) (see Distributed program link (DPL))
DPL enables CICS application programs to issue EXEC CICS LINK commands in either direction between System/390 and non-System/390 CICS systems.
Asynchronous processing (see Asynchronous processing)
Asynchronous processing is supported between System/390 and non-System/390 CICS systems. The initiating request can flow in either direction.
Distributed transaction processing (see Distributed transaction processing (DTP))
Distributed transaction processing, using mapped conversations, is supported between System/390 and non-System/390 CICS systems. The initiating request can flow in either direction.
[[ Contents Previous Page | Next Page Index ]]