Scenario 2

The next few example scenarios will use the CICS/IMS regions shown in Figure 1.

Figure 1. Scenarios 2, 3, 4, 5: CICS/IMS regions

Scenarios 2, 3, 4, 5: CICS/IMS Regions: CICSREGP (service class = PRODRGNS) and CICSREGT (service class = TESTRGNS).

Suppose you have the following 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       ______   NO
  ____  1  TN         CC         ___    TRXCC       ______   NO

Suppose you have the following STC classification rules to classify the CICS regions:

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    ______   NO        TRANSACTION
  ____  1  TN         CICSREGT   ___    TESTRGNS    ______   NO        TRANSACTION

Suppose the transaction service classes are defined as follows. (Only TRXAA is shown here. The definitions for TRXBB and TRXCC would also have NO specified in the Cpu Critical field.)

Service Class Name . . . . . . TRXAA     (Required)
Description  . . . . . . . . . Transactions AA1, AA2__________
Workload Name  . . . . . . . . JES       (name or ?)
Base Resource Group  . . . . . ________  (name or ?)
Cpu Critical . . . . . . . . . NO        (YES or NO)

Suppose the regions' service classes are defined as follows (PRODRGNS shown here, TESTRGNS would look the same):

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

In this scenario, assume that the regions are running normal, non-conversational transactions. Response time goals are appropriate, and there is enough activity so that WLM can manage the regions as servers virtually all of the time. Transaction AA1 is very important to the business, and you wish to give it both storage and CPU protection.

In this case, protection on a transaction service class level is sufficient. This approach allows you to focus on protecting specific transactions rather than the regions that process them. The protection will be inherited by any regions in which the transactions run, as long as WLM is allowed to manage the region to the transactions' goals. (Scenario 5 shows what happens when WLM is not allowed to manage the region to the transactions' goals.)

Assign storage protection to transaction AA1 using the CICS classification rule:

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   YES
  ____  1  TN         AA2        ___    TRXAA       AA2RPT   NO
  ____  1  TN         BB         ___    TRXBB       ______   NO
  ____  1  TN         CC         ___    TRXCC       ______   NO

Transaction service class TRXAA runs only in the CICSREGP region, and not in CICSREGT; therefore, CICSREGP will inherit the storage protection, and CICSREGT will not inherit the storage protection.

Assign CPU protection to the transaction service class TRXAA in the service class definition:

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

Any region serving any TRXAA transactions, even one serving AA2 only, inherits CPU protection. As was true for storage protection, CICSREGT will not inherit CPU protection because it does not serve transaction service class TRXAA.

Reporting products which display data about the regions themselves will not show that storage and CPU protection was specified, but will show that they were protected while serving the transactions. (See Reporting.) Service class reports will show the storage and CPU protection assigned to the TRXAA transaction service class.