This scenario is similar to Scenario 2, but here you'll see what happens when WLM is not allowed to manage one of the regions to the transactions' goals, and how this will prevent protection of a transaction. In this case, assume that it is transaction BB that you wish to give both storage and CPU protection, and assume that at the same time you have exempted region CICSREGT from management to the transaction response time goals.
Subsystem Type . : CICS Fold qualifier names? Y (Y or N)
Description . . . IBM-defined subsystem type
-------Qualifier--------- -------Class------ Storage
Action Type Name Start Service Report Critical
____ 1 TN AA1 ___ TRXAA AA1RPT NO
____ 1 TN AA2 ___ TRXAA AA2RPT NO
____ 1 TN BB ___ TRXBB ______ YES
____ 1 TN CC ___ TRXCC ______ NO
Service Class Name . . . . . . TRXBB (Required)
Description . . . . . . . . . CICS Transactions_______________
Workload Name . . . . . . . . CICS (name or ?)
Base Resource Group . . . . . ________ (name or ?)
Cpu Critical . . . . . . . . . YES (YES or NO)
Subsystem Type . : STC Fold qualifier names? Y (Y or N)
Description . . . IBM-defined subsystem type
-------Qualifier--------- -------Class------ Storage Manage Region
Action Type Name Start Service Report Critical Using Goals Of:
____ 1 TN CICSREGP ___ PRODRGNS ______ YES TRANSACTION
____ 1 TN CICSREGT ___ TESTRGNS ______ YES REGION
As illustrated in Figure 1, transaction BB runs in both regions, CICSREGP and CICSREGT. Since WLM will not manage region CICSREGT to transaction response times, it will not inherit storage or CPU protection from the TRXBB transaction service class. Transaction BB will therefore not run with storage or CPU protection in region CICSREGT.