This section presents a brief overview of the ways in which subsystems can be connected for intersystem communication. There are three basic forms to be considered:
A possible configuration is shown in Figure 3.
ISC within a single operating system (intrahost ISC) is possible through the application-to-application facilities of ACF/VTAM. In Figure 3, these facilities can be used to communicate between CICSA and CICSB, between CICSC and IMSA, and between CICSD and CICSE.
In an MVS™ system, you can use intrahost ISC for communication between two or more CICS® systems (although MRO is a more efficient alternative) or between, for example, a CICS system and an IMS™ system.
From the CICS point of view, intrahost ISC is the same as ISC between systems in different VTAM® domains.
An IBM® 3725 can be configured with a multichannel adapter that permits you to connect two VTAM domains (for example, VTAM1 and VTAM2 in Figure 3) through a single ACF/NCP/VS. This configuration may be useful for communication between:
Direct channel-to-channel communication is available between systems that have ACF/VTAM installed.
This is the most typical configuration for intersystem communication. For example, in Figure 3, CICSD and CICSE can be connected to CICSA, CICSB, and CICSC in this way. Each participating system is appropriately configured for its particular location, using MVS or Virtual Storage Extended (VSE) CICS or IMS, and one of the ACF access methods such as ACF/VTAM.
For a list of the CICS and non-CICS systems that CICS Transaction Server for z/OS® can connect to via ISC, see Intersystem communication. For detailed information about using ISC to connect CICS Transaction Server for z/OS to other CICS products, see the CICS Family: Communicating from CICS on System/390® manual.