Using a “hub”

For LU6 connections initiated by a generic resource member, where the partner is not itself a CICS® Transaction Server for z/OS® generic resource, the partner must know the member TOR by its generic resource name.

The requirement therefore applies when a generic resource member initiates any of the following kinds of connection:
  • APPC connections to single systems
  • APPC connections to members of a CICSplex that are not also generic resource members
  • All LU6.1 connections.

Because (unless the partner is also a CICS TS for z/OS generic resource) an attempt by a generic resource member to connect to an LU6 partner will succeed only if the partner knows the TOR by its generic resource name, it follows that the partner can accept a connection to only one member of the generic resource at a time. In a configuration in which more than one member of a generic resource must connect to a remote system, you can choose a region within the CICSplex to act as a network hub. This means that all generic resource members daisy-chain their requests for services from remote systems through the hub.

The network hub can be a member of the generic resource, in which case it is necessary to install a z/OS Communications Server generic resource resolution exit program to direct any incoming binds from LU6 partners that know us by our generic resource name to the network hub region.

An alternative solution is to have a network hub that is not a member of the generic resource. This avoids the need for the z/OS Communications Server generic resource resolution exit program, but requires that LU6 partners that may initiate connections to the CICSplex log on using the applid of the network hub region.

Figure 1 shows a network hub that is not a member of the generic resource.
Figure 1. A network hub. Hubs are typically used for outbound LU6 requests from members of a generic resource group to a system that is not a member of a CICS Transaction Server for z/OS generic resource.
The picture shows a CICSplex, CIC1, containing three AORs and four TORs. Within the CICSplex, the regions are interconnected by MRO links. Three of the TORs are members of a generic resource group, CICSG, but the fourth (the hub TOR, H) is not. The hub TOR has an LU6 connection to an external region, R, that is not a member of a CICS TS 390 generic resource. The TORs in the generic resource group daisy-chain their requests to R through H.

In Figure 1, the regions in CICSplex CIC1 are connected by MRO links. The terminal-owning regions T1, T2, and T3 are members of the generic resource group, CICSG, but the hub TOR, H, is not. H has an LU6.1 or APPC connection to the remote region, R. The TORs daisy-chain their requests to R through H.



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