Connections between subsystems

Subsystems can be connected for intersystem communication in three basic forms.

A possible configuration is shown in Figure 1.
Figure 1. A possible configuration for intercommunicating systems
The picture shows two IBM 3725s. The first supports two operating systems—z/OS and OS/390. On z/OS, there are two regions, CICSA and CICSB, and a z/OS Communications Server SNA domain, VTAM1 (VTAM is now the z/OS Communications Server). On OS/390, there is one region, CICSC, an IMS region, IMSA, and an SNA domain, VTAM2. The first 3725 is configured with a multichannel adaptor that connects the two SNA domains. The second 3725 supports one operating system—VSE. On VSE, there are two CICS/VSE regions, CICSD and CICSE, and an SNA domain, VTAM3.The two 3725s are connected.

Single operating system

ISC in a single operating system (intrahost ISC) is possible through the application-to-application facilities of ACF/SNA. In Figure 1, 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 SNA domains.

Physically adjacent operating systems

You can configure an IBM® 3725 with a multichannel adapter that permits you to connect two SNA domains (for example, VTAM1 and VTAM2 in Figure 1) through a single ACF/NCP/VS. This configuration might be useful for communication between these systems:
  • A production system and a local but separate test system
  • Two production systems with differing characteristics or requirements

Direct channel-to-channel communication is available between systems that have ACF/SNA installed.

Remote operating systems

The most typical configuration for intersystem communication is between remote operating systems. For example, in Figure 1, 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/SNA.

For a list of the CICS and non-CICS systems to which CICS Transaction Server for z/OS® can connect to using ISC, see Communication between systems.



dfht1k6.html | Timestamp icon Last updated: Sunday, 4 June 2017