Scenario 3

In this scenario, again using the CICS® regions shown in Figure 1, assume that the regions are running non-conversational transactions, but with periods of low activity during which WLM may stop managing them as servers. During this time, it is more likely that the regions' pages will be stolen by competing workloads. In this scenario, assume that transaction BB needs storage and CPU protection.

Protection on a transaction service class level is once again useful, ensuring that the transactions will be protected wherever they run. The regions themselves should also be protected, as WLM may not manage them as servers during the low activity periods.

Assign storage protection to transaction BB using the CICS classification rules:

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

Also, assign storage protection to the regions themselves using the STC classification rules:

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       TRANSACTION

Assign CPU protection to the transaction service classes TRXBB (the Cpu Critical field in the TRXAA and TRXCC service class definitions would remain set to 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)

And also to the regions themselves (PRODRGNS shown here, TESTRGNS would also specify YES in the Cpu Critical field):

Service Class Name . . . . . . PRODRGNS  (Required)
Description  . . . . . . . . . CICS Regions____________________
Workload Name  . . . . . . . . STC       (name or ?)
Base Resource Group  . . . . . ________  (name or ?)
Cpu Critical . . . . . . . . . YES       (YES or NO)

Note that since both CICSREGP and CICSREGT run transaction BB, both regions must be protected.

Reporting products which display data about the regions will show that both CPU and storage protection was specified. (See Reporting.) While the regions are serving transactions, protection will occur if either the regions themselves or any of their served transaction service classes are protected.