Scenario 4

In this scenario, again using the CICS® regions shown in Figure 1, assume that the regions are running conversational transactions, and response time goals are not appropriate. By exempting the regions from management to the transaction response time goals, the regions will instead be managed according to the goal of the service class assigned to those regions. (If either storage or CPU protection is needed, that goal must be a velocity goal, since discretionary goals are not eligible for storage or CPU protection.) In this scenario, assume that only the production region CICSREGP needs protection.

Assign storage protection to the CICSREGP region. Also, in the same panel, exempt both regions from management to the transaction response time goals:

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

Assign CPU protection to the PRODRGNS service class (the Cpu Critical field in the TESTRGNS service class definitions would remain set to NO):

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

Reporting products which display data about the regions will show that CPU or storage protection was specified based on the regions' storage protection value and the CPU protection value of the regions' service classes. (See Reporting.)