Separating a Link3270 bridge workload

You can separate Link3270 bridge workloads by user ID, transaction group, or LU name.

About this task

You can separate by LU name only if you are overriding the NETNAME that the bridge generates automatically. Be aware of the restrictions on the use of LUNAME when separating Link3270 bridge workloads. For more information, see Separating Link3270 bridge workloads. For Link3270 bridge workloads, the LU name is the eight–character NETNAME of the terminal running the client transaction that started the Link3270 bridge, rather than the NETNAME of the bridge facility itself.

To separate by bridge facility NETNAME, you must modify the EYU9WRAM module. For more information, see Separating Link3270 bridge workloads. CICS® routes all transactions running under the same bridge facility to the same target region. You cannot force them to go to different regions.

The following example describes how to separate a bridge workload by userid and transaction group. The example uses the same configuration as that described in Creating workload management definitions using the WUI.

Add the following definitions to the definitions that you created in Creating workload management definitions using the WUI.

Procedure

  1. Create a transaction group.
    1. From the Web User Interface main menu, click Administration views > Workload manager administration views > Transaction group definitions. The Transaction group definition view opens, listing any transaction groups already defined in PLXPROD1.

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

    2. Scroll to the bottom of the view, click Create, and provide the following information:
      Transaction group name
      TRGBRI01
      Description
      Link3270 bridge transaction group
      Affinity relation and lifetime checking status
      ACTIVE
      Primary search criterion
      User ID
      Automatic affinity creation option
      N/A

      You can leave the remaining fields or accept the defaults.

    3. Click Yes. The Transaction group definition view is redisplayed, now showing the name of the transaction group TRGBRI01.

      Leave the Affinity relationship and Affinity lifetime fields blank and the Automatic affinity creation option field set to N/A because CICSPlex® SM does not handle affinities between Link3270 bridge transactions.

    Note: If you want to separate by LUNAME, you must enter LUNAME in the Primary search criterion field of the Transaction group definition create view.
  2. Identify the transactions in group TRGBRI01.
    1. In the Transaction group definition view, select the entry for TRGPAY03, and click Add transaction.
    2. Type the name BRI1 in the Transaction name field, and click Yes to confirm. The Transaction group definition view is redisplayed.
  3. Repeat the previous two steps for any further transactions that you want to be routed to different regions.
  4. Create a workload definition.
    1. From the main menu, click Administration views > Workload manager administration views > Definitions. The Workload management definition view opens.
    2. Scroll to the bottom of the view, click Create, and provide the following information:
      Workload management definition name
      WLDBRI01
      Description
      Separate Link3270 bridge activities
      Transaction group name
      TRGBRI01
      Terminal LU name
      *
      User ID
      BRIUSER1
      BTS process type
      *
      Scope name of set of target systems
      CICSPA01

      These values indicate that transactions in group TRGBRI01 entered by BRIUSER1 are to be routed to CICSPA01.

    3. Click Yes to confirm.
    Note: If you want to separate by LUNAME, you must enter the LUNAME in the Terminal LU name field of the Workload management definition create view.
  5. Repeat the previous step for any further transaction groups you have created for transactions that are to be routed to different regions.
  6. Create a workload group. A workload group is essential if you want a workload definition to be installed automatically when the routing region that is routing the transactions is started.
    1. From the main menu, click Administration views > Workload manager administration views > Groups. The Workload management group view opens, listing any workload groups already created in PLXPROD1.
    2. Click Create and type in the following information:
      Workload management group name
      WLGBRI01
      Description
      Workload Group for WLDBRI01
    3. Click Yes to confirm. The Workload management group view is redisplayed.
  7. Add the workload definition WLDBRI01 and any other workload definitions you have created to WLGBRI01.
    1. From the main menu, click Administration views > Workload manager administration views > Definitions. The Workload management definition view opens.
    2. Select the entry for WLDBRI01, click Add to WLM group, and provide the following information:
      Workload management definition name
      WLDPAY01
      Description
      Link3270 bridge workload definition
      Resource group name
      WLGBRI01
    3. Click Yes to confirm.
    4. Repeat for any additional workload definitions that you created earlier.
  8. Add workload group WLGBRI01 to workload specification BRSPEC01.
    1. From the main menu, click Administration views > Workload manager administration views > Groups. The Workload management (WLM) group view opens.
    2. Select the entry for WLGBRI01, click Add to WLM specification, and type BRSPEC01 in the Specification name field.
    3. Click Yes to confirm.
  9. Install definition into the active workload.
    1. From the main menu, click Administration views > Workload manager administration views > Definitions. The Workload management definition view opens.
    2. Select the entry for WLDBRI01, and click Install to install it into the active workload. Click Yes to confirm. The workload separation definitions you created take effect immediately.
    3. Click Yes to confirm.

What to do next

You can check that the workload definition is active using the Workload definition installed in active workload view.



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