Common Communications Interface › Configuration › How CAICCI Routes Control Information

How CAICCI Routes Control Information

Mainframe CAICCI implementations maintain a replicated, dynamic, real‑time directory of applications and network resources to manage communications. Many of the CAICCI internal algorithms require a detailed representation of these objects in order to locate applications and make optimum routing decisions.

Usually, CAICCI maintains the control information for its directory using an ongoing exchange of state change messages. In large or very dynamic networks, transmitting these state changes may consume significant network resources. So, by default, CAICCI only exchanges information among networked computers that are connected directly to one another.

If your networked computers are not connected directly, you can designate one or more CAICCI gateways. Gateways are systems that coordinate state information across CAICCI subnets. A gateway lets CAICCI forward state change messages among computers that cannot communicate with one another directly.

Example: Direct Connections

Five computers are connected directly to one another using CAICCI. They are interconnected using TCP/IP, SNA, or parallel sysplex protocols for communications. In this configuration, CAICCI can maintain accurate state information.

Example: Gateway

Five computers (CPUA, CPUB, CPUC, CPUD, and CPUE) are connected directly to one another using CAICCI. They are interconnected using SNA for communications. The computer, CPUA, has several Windows, UNIX, and Linux computers connected to it. The CA solutions running on Windows, UNIX, and Linux want to communicate with CPUA and CPUB only. You can use the CAICCI GATEWAY control option.

The CAICCI control option member for CPUA can contain the following statements:

SYSID(CPUA)
PROTOCOL(VTAM,applid_a,1,CPUA)
PROTOCOL(TCPIPGW)
GATEWAY(LU0,applid_b,1,CPUB)
NODE(LU0,applid_c,1,CPUC)
NODE(LU0,applid_d,1,CPUD)
NODE(LU0,applid_e,1,CPUE)
CONNECT(CPUB,CPUC,CPUD,CPUE)

The CAICCI control option member for CPUB can contain the following statements:

SYSID(CPUB)
PROTOCOL(VTAM,applid_b,1,CPUB)
GATEWAY(LU0,applid_a,1,CPUA)
NODE(LU0,applid_c,1,CPUC)
NODE(LU0,applid_d,1,CPUD)
NODE(LU0,applid_e,1,CPUE)
CONNECT(CPUA,CPUC,CPUD,CPUE)

The CAICCI control option member for CPUC can contain the following statements:

SYSID(CPUC)
PROTOCOL(VTAM,applid_c,1,CPUC)
NODE(LU0,applid_a,1,CPUA)
NODE(LU0,applid_b,1,CPUB)
NODE(LU0,applid_d,1,CPUD)
NODE(LU0,applid_e,1,CPUE)
CONNECT(CPUA,CPUB,CPUD,CPUE)

The CAICCI control option members for CPUD and CPUE contain statements similar to those for CPUC.