Dynamic routing of a peer-to-peer DPL request

This example describes how to use the Web User Interface (WUI) to set up dynamic routing for a peer-to-peer DPL request, and to use the GOAL algorithm to select the target region.

Note: You should check the system requirements before trying to dynamically route peer-to-peer DPL requests. See CICSPlex SM workload requirements.

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 with EXEC CICS START TERMID. 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 want 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:
  • A Service Class of Medium with an average response time of 4 seconds.
  • A classification rule associating Classification Subsystem CICS with transaction ID PAY1 and Service Class Medium.

For more information about Service Classes, see the information about the goal algorithm in Management of the work in a workload.

In CICSPlex® SM:
  1. The first step is to set the dynamic routing status value for program PAYPROG1. To do this:
    • From the main menu, click Administration views > Basic CICS resource administration views > Resource definitions > Program definitions. This opens the Program definitions tabular view.

      If the current context is not PLXPROD1, specify PLXPROD1 in the Context field and click Refresh.

    • Click the Record check box beside the entry for PAYPROG1 and click the Update... button.
    • Set the Dynamic routing status field to NO from the drop-down box.
    • Click Yes to confirm.
  2. Install program definitions:
    • From the Program definitions tabular view, click the Record check box beside the entry for PAYPROG1 and click the Install... button.
    • Type CICSPA01 in the Target scope value field.
    • Click Yes to confirm.

    Repeat this step to install PAYPROG1 in target scopes CICSPA02 and CICSPA03.

    For details of defining and installing program definitions, see Creating resources with BAS: PROGRAM resource definitions.

    You don't need to install program definition PAYPROG2 in the regions, but if you do, PAYPROG2 should be defined as dynamic.

  3. Install the transaction definition:
    • From the main menu, click Administration views > Basic CICS resource administration views > Resource definitions > Transaction definitions. This opens the Transaction definitions tabular view.

      If the current context is not PLXPROD1, specify PLXPROD1 in the Context field and click Refresh.

    • From the Transaction definitions tabular view, Click the Record check box beside the entry for PAY2 and click the Install... button.
    • Type CICSPA01 in the Target scope value field.
    • Click Yes to confirm.

    The transaction definition should point to the mirror program DFHMIRS.

    Repeat this step to install PAY2 in target scopes CICSPA02 and CICSPA03.



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