Modify Rules for the Subsystem Type Row 1 to 2 of Command
===> ____________________________________________ SCROLL ===> PAG
Subsystem Type . : STC Fold qualifier names? Y (Y or N)
Description . . . IBM-defined subsystem type
Action codes: A=After C=Copy M=Move I=Insert rule
B=Before D=Delete row R=Repeat IS=Insert Sub-rule
<=== More
-------Qualifier--------- Storage Manage Region
Action Type Name Start Critical Using Goals Of
____ 1 SY SYST1 ___ NO TRANSACTION
____ 2 TN CICSTEST ___ NO REGION
____ 2 TN CICS* ___ YES TRANSACTION
____ 2 TN TOR ___ NO BOTH
____ 2 TN AOR* ___ NO TRANSACTION
If you specify TRANSACTION in this field (the default), the region will be managed as a CICS/IMS transaction server by WLM. If you specify REGION in this field, the region will be managed to the performance goal of the service class assigned to that region (address space). In other words, it will not be managed as a CICS/IMS transaction server by WLM.
If you specify BOTH in this field, the region will also be managed to the performance goal of the service class assigned to that region, but it will nevertheless track all transaction completions so that WLM can still mange the CICS® service classes with response time goals. Option BOTH should only be used for CICS TORs. All AORs should remain at the default TRANSACTION.
If you specify REGION, only the information in the SCPER report will change. Transaction response times reported by these regions will not be reported in any service class. This response time data will still be reported in the RCLASS report for the transaction report class, and the service classes served by the region will still be reported in the SCLASS report for the service class in which the region is running. In both of these cases, this information will be useful if you are migrating the CICS/IMS region to transaction response time management, and need both a transaction response time benchmark and a list of the service classes the region is serving.