This example describes how to use the end user interface (EUI)
to set up dynamic routing for a peer-to-peer DPL request, and to use the goal
algorithm to select the target region.
In this example, transaction PAY1 runs program PAYPROG1, which issues an EXEC CICS® LINK command to program PAYPROG2. You require transaction PAY1 to have a response time of 4 seconds.
This example uses the environment that was used for Dynamic routing an EXEC CICS START TERMID command. However, because this is a peer-to-peer dynamic linking request, only the AORs are involved and each AOR may act as a requesting, routing, or target region.
As you wish to use the goal algorithm, you need to define, in MVS™ Workload Manager, a Service Class with the required response time and allocate that Service Class to the transaction. For example, you could specify:
For more information about Service Classes, see topic Service classes.
In CICSPlex® SM:
Install the transaction definition for PAY2 in all regions with the Dynamic and Routable attributes set to No. The transaction definition should point to the mirror program DFHMIRS.
You don't need to install program definition PAYPROG2 in the regions, but if you do, PAYPROG2 should be defined as dynamic.