You can use transaction classes to classify client workload for workload management (WLM). The workload that WLM manages consists of different transactions that are targeted to separate servants, each with goals defined by specific service classes. The service classes chosen also determines the WLM goal when Java Garbage Collection (GC) is running, which can be CPU intensive. You do not want to set a servant higher in the service class hierarchy than more important work such as production WebSphere, CICS, or IMS transaction servers.
You must define the service objectives (goals) for your service classes. You must also define the service objectives of your servers. For more information about defining service objectives (goals) for each service class, see the z/OS MVS Planning: Workload Management book, SA22-7602, for example at http://publibz.boulder.ibm.com/epubs/pdf/iea2w131.pdf, or the z/OS WLM Web page at http://www.ibm.com/servers/eserver/zseries/zos/wlm/.
Each transaction is dispatched in its own WLM enclave in a servant process, and is managed according to the goals of its service class. The service class chosen also determines the WLM goal when Java Garbage Collection (GC) is running, which can be CPU intensive.
You should classify the servants to a high STC importance service class so that they are initialized quickly when WLM determines they are needed. However, you do not want to set a servant higher in the service class hierarchy than more important work such as CICS, or IMS transaction servers.
Controllers perform some processing as they receive work into the system, manage the transport handlers, classify a work item, and handle housekeeping tasks. Therefore, controllers should also be classified a high STC importance service class.
You can use the WLM CB-type classification criteria to classify work items:
To classify work using server and userid criteria, use a combination of the WLM Workload Classification rules in the WLM ISPF dialog panels. For more information about defining WLM Classification rules, see Workload management (WLM) and its related article that includes an example of classification rules.
To classify work using transaction classes, you define and use transaction class mappings, as described in this task. The following steps are used to classify work using transaction classes:
--------Qualifier-------- -------Class-------- Action Type Name Start Service Report DEFAULTS: OPS_DEF ________ _____ 1 TN %%DMN ___ OPS_HIGH RWSDMN _____ 1 TN T5SRV* ___ OPS_MED RT5SRV _____ 1 TN WS%%%% ___ SYSSTC RWSCTLR ____ 1 TN WS%%%%S ___ OPS_HIGH RWSSRVR
The following table shows classification rules for CB-type work in which the default service class is WSMED and has a reporting class of RWSDEFLT. Work run in the WSPROD WebSphere server is classified as WSMED with a reporting class of RWSPROD, unless it has a transaction class of TCLASS1, TCLASS2, or TCLASS2 assigned through the transaction class mapping file below.
Qualifier Qualifier Start Service Report # type name position Class Class - --------- -------- -------- -------- -------- Default: WSMED RWSDEFLT 1 CN WSPROD 1 WSMED RWSPROD 2 . TC . TCLASS1 WSFAST RWSPRD1 2 . TC . TCLASS2 WSMED RWSPRD2 2 . TC . TCLASS5 WSSLOW RWSPRD5 1 CN WSTEST 1 WSSLOW RTSTEST 2 . UI . USER1 WSMED RTSTSTU2 2 . TC . TCLASS5 WSSLOW RTSTST5
TransClassMap www.ibm.com:80 /Webap1/myservlet TCLASS1 TransClassMap www.ibm.com:* /Webap1/myservlet TCLASS2 TransClassMap *:443 * TCLASS3 TransClassMap *:* /Webap1/myservlet TCLASS4 TransClassMap www.ibm.com:* /Webap5/* TCLASS5 TransClassMap * * TCLASS6
In this information ...Related tasks
Classifying z/OS workload | IBM Redbooks, demos, education, and more |