How the distributed routing program relates to the dynamic routing program
The supplied user-replaceable routing programs, DFHDYP and DFHDSRP complement each other. Use DFHDYP for dynamic routing and DFHDSRP for distributed routing.
- The dynamic routing program, DFHDYP
- Can be used to route:
- Transactions started from terminals
- Transactions started by terminal-related START commands
- Program-link requests.
- The distributed routing program, DFHDSRP
- Can be used to route:
- BTS processes and activities
- Non-terminal-related START requests.
The two routing programs:
- Are specified on separate system initialization parameters.
- Are passed the same communications area. Certain fields that are meaningful to one program are not meaningful to the other.
- Are invoked at similar points - for example, for route selection, route selection error, and (optionally) at termination of the routed transaction or program-link request.
Together, these three factors give you a good deal of flexibility.
You could, for example, do any of the following:
- Use different user-written programs for dynamic and distributed routing.
- Use the same user-written program for both dynamic and distributed routing.
- Use a user-written program for dynamic routing and the CICSPlex® SM routing program for distributed routing, or vice versa.
The distributed routing program differs from the dynamic routing
program in several important ways:
- The dynamic routing program is invoked only if the resource (the transaction or program) is defined as DYNAMIC(YES). The distributed routing program, however, is invoked (for eligible non-terminal-related START requests and BTS activities) even if the associated transaction is defined as DYNAMIC(NO) - though it cannot route the request. This means that the distributed routing program is better able to monitor the effect of statically routed requests on the relative workloads of the target regions.
- Because the dynamic routing program uses the hierarchical "hub" routing
model - one routing program controls access to resources on several
target regions - the routing program that is invoked at termination
of a routed request is the same that was invoked for route selection.
The distributed routing program, however, uses the distributed model, which is a peer-to-peer system - the routing program itself is distributed. The routing program that is invoked at initiation, termination, or abend of a routed transaction is not the same program that was invoked for route selection - it is the routing program on the target region.
- The distributed routing program is invoked at more points than the dynamic routing program. When and where the distributed routing program is called shows the points at which the distributed routing program is invoked, and the region on which each invocation occurs.