Honoring a pseudoconversational transaction
This example describes how to use the Web User Interface (WUI) to ensure that multiple transactions, among which there is an affinity, are routed to the same target region.
As before, you are working in CICSplex PLXPROD1 and are routing transactions from CICSPT01 to the target regions in CICS system group CSGTGTS1.
- Create a transaction group:
- From the main menu, click Administration views > Workload manager
administration views > Transaction group definitions. This opens
the Transaction group definitions tabular view.
If the current context is not PLXPROD1, specify PLXPROD1 in the Context field and click Refresh.
- Click the Create... button, and provide the following information:
Name TRGPAY03 Description Pseudoconversational transaction Affinity relation and lifetime checking status ACTIVE Primary search criterion USERID Affinity relationship USERID Affinity lifetime PCONV Notice that the Affinity relationship and Affinity lifetime fields must be completed. These values tell CICSPlex® SM that the transactions in this group constitute a pseudoconversational transaction (PCONV), and that this affinity lasts while those transactions are coming from the same user ID (USERID). If one of them is initiated from a different user ID, CICSPlex SM can select a different target region. Of course, the same type of affinity will then come into play in that second target region. You can ignore any fields that have been left blank or accept the defaults.
- Click Yes to confirm. The Transaction group definitions tabular view is redisplayed.
- From the main menu, click Administration views > Workload manager
administration views > Transaction group definitions. This opens
the Transaction group definitions tabular view.
- Identify the transactions that belong to group TRGPAY03:
- In the Transaction group definitions tabular view, select the entry for TRGPAY03 and click the Add transaction... button.
- In the Transaction name field, type in the name of the
first transaction PAY2 and click Yes to confirm.
Repeat this step for three more transactions: PAY3, PAY4, and PAY5.
You can see that PAY2 starts the pseudoconversation and PAY5 ends it.
- Create a workload definition:
- From the main menu, click Administration views > Workload manager administration views > Definitions. This opens the WLM definitions view, listing any workload definitions already created in PLXPROD1.
- Click the Create... button, and provide the following information:
Workload management definition WLDPAY03 Description TRGPAY03 to the same target region Transaction group name TRGPAY03 Scope name of set of target systems CSGTGTS1 - Click Yes to confirm.
- Add the workload definition to the workload group:
- From the main menu, click Administration views > Workload manager administration views > Definitions to open the WLM definitions tabular view.
- Select the entry for WLDPAY03 and click the Add to WLM group... button.
- In the Resource group name field, type WLGPAY01.
- Click Yes to confirm.
- Because group WLGPAY01 is already associated with the active workload
WLSPAY01, changes you make to that group will not take effect until
the routing region CICSPT01, and the target regions in CICS system
group CSGTGTS1, are next started. To make the new workload definition
take effect immediately, you must install it explicitly in WLSPAY01.
To install the new workload definition into the active workload:
- Open the WLM definitions view again, select the entry for WLDPAY03, and click the Install... button.
- In the Workload name field, type in WLSPAY01, and in the Workload owner field, type in the SYSID of the system on which the workload specification WLSPAY01 was created.
Because you have explicitly installed the workload definition WLDPAY03 in the active workload WLSPAY01, CICSPlex SM is able to honor this pseudoconversational transaction immediately. Be aware that you are able to use the single workload specification WLSPAY01 for both workload routing and workload separation because you did not specify default Affinity relationship and Affinity lifetime values in WLSPAY01. Had you done so, you would have had to create different workload specifications for workload routing and workload separation.