The traditional hub model

The traditional hub model is the model used for the dynamic routing of transactions, EXEC CICS START commands associated with a terminal, and inbound client DPL requests. The request is initiated in the requesting region, typically a TOR, which also acts as the routing region. The request is routed to a target region, selected from the specified target group, where the program is executed.

The traditional hub model is shown in Figure 1.

The “hub” model is hierarchical, in which routing is controlled by one region (the routing region, that is, the TOR). Normally, a routing program runs only in the routing region. This model has the advantage of being relatively simple to implement. For example, compared with the distributed model, there are few inter-region connections to maintain. The disadvantages of the hub model are:
  • If you use only one hub to route transactions and program-link requests across your target regions, the hub routing region is a single point-of-failure.
  • If you use more than one hub to route transactions and program-link requests across the same set of target regions, you may have problems with distributed data. For example, if the routing program keeps a count of routed transactions for load balancing purposes, each hub routing region will need access to this data, which may be maintained in a local temporary storage queue.
Figure 1. Dynamic routing using a hub routing model
The figure shows a TOR which is acting as a requesting region and a routing region and where the dynamic routing program is running. The TOR is linked to several possible target regions. The the hub method is described in the preceding text.


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