+

Search Tips   |   Advanced Search

(ZOS) RMF Workload Activity reports and RMF Monitor III

Performance metrics include transaction rates and response times. Resource utilization includes CPU, I/O (channel), and storage utilization.

Transactions/second

This is shown in the AVG, MPL, and AVG ENC fields which is equal to the average number of enclaves in the period in the RMF™ Monitor.

Response times

The actual response times of the WLM transaction is shown in the TRANS.-TIME SS.TTT' column n the RMF Monitor and are measured in milliseconds. (This also includes time waiting on WLM queue.)

Service Rates

Resource utilization in CPU service units, and Service Units per Sec. The APPL% field shows the number of processor engines (CPs) required to drive the work in the service (report) class.

Controller Regions Example: Here is the report for the WebSphere controller regions which were all assigned a particular reporting class according to the STC classification rules based on the started class jobname. There is only one transaction active in the system, there are no response time figures, and required 37.2% of a processor engine to support its work.

    TRANSACTIONS    TRANS.-TIME  SS.TTT   ---SERVICE--   --SERVICE RATES--
    AVG      1.00   ACTUAL            0   IOC        0   ABSRPTN     89615
    MPL      1.00   EXECUTION         0   CPU   522567   TRX SERV    89615
    ENDED       0   QUEUED            0   MSO    10159K  TCB          39.9
    END/S    0.00   R/S AFFINITY      0   SRB    61728   SRB           4.7
    #SWAPS      0   INELIGIBLE        0   TOT    10743K  RCT           0.0
    EXCTD       0   CONVERSION        0   /SEC   89630   IIT           0.0
    AVG ENC  0.00   STD DEV           0                  HST           0.0
    REM ENC  0.00                                        APPL %       37.2

Servant Regions Example: Here is the report for the WebSphere servant regions which were all assigned a particular reporting class according to the STC classification rules based on the stared class jobname. There are only two transactions active in the system (meaning there were two servant regions), there are no response time figures, and they required 10% of a processor engine to support their work.

    TRANSACTIONS    TRANS.-TIME  SS.TTT   ---SERVICE--   --SERVICE RATES--
    AVG      2.00   ACTUAL            0   IOC        0   ABSRPTN    122075
    MPL      2.00   EXECUTION         0   CPU   143957   TRX SERV   122075
    ENDED       0   QUEUED            0   MSO    29113K  TCB          11.0
    END/S    0.00   R/S AFFINITY      0   SRB    12460   SRB           1.0
    #SWAPS      0   INELIGIBLE        0   TOT    29270K  RCT           0.0
    EXCTD       0   CONVERSION        0   /SEC  244192   IIT           0.0
    AVG ENC  0.00   STD DEV           0                  HST           0.0
    REM ENC  0.00                                        APPL %       10.0

WebSphere Transactions (Enclaves) Example: Here is the report for the real WebSphere transaction work which runs as enclaves in this particular reporting class. The average number of these kind of transactions active in the system was 241.52, the average response time was 276 milliseconds, and required 2.129 processor engines to support this work.

    TRANSACTIONS    TRANS.-TIME  SS.TTT   ---SERVICE--   --SERVICE RATES--
    AVG    241.52   ACTUAL          276   IOC        0   ABSRPTN       115
    MPL    241.52   EXECUTION       272   CPU     3343K  TRX SERV      115
    ENDED  106717   QUEUED            4   MSO        0   TCB         255.5
    END/S  890.32   R/S AFFINITY      0   SRB        0   SRB           0.0
    #SWAPS      0   INELIGIBLE        0   TOT     3343K  RCT           0.0
    EXCTD       0   CONVERSION        0   /SEC      17   IIT           0.0
    AV ENC 241.52   STD DEV          66                  HST           0.0
    REM ENC  0.00                                        APPL %      212.9

Delays Example: The QMPL field in the following report means that the server was waiting for a Server Region to select work off the WLM queue. Here is a queue delay report which shows that work was delayed 23.5% of the time waiting for the CPU and 12.6% of the time waiting for a servant region:

             EX   PERF   AVG   --USING%--  ----- EXECUTION DELAYS % -----
             VEL  INDX  ADRSP   CPU   I/O  TOTAL   CPU QMPL
    GOAL    40.0%
    ACTUALS 45.3%  .89   13.4   0.1   0.0   36.1  23.5 12.6

Started Class Classification Example: Here is an example of the STC classification rules/panel in WLM which can be used to classify the non-enclave time in the websphere server regions. WebSphere production controller region with a jobname of WSPRODC is assigned a service class of STCCR and reporting class of RCTLREG, production controller region with a jobname of WSPRODC is assigned a service class of STCSR and reporting class of RSRVREG, and testregions (servant and controllers) with a jobname starting with WSTare assigned a service class of STCWSTST and reporting class of RWSTST.

  Subsystem Type . . . . . . . : STC
  Description  . . . . . . . . . All started tasks
    -------Qualifier-------------            -------Class--------
    Type       Name     Start                Service     Report
    Type       Name     Start                Service     Report
                                   DEFAULTS: STCMED__    RSTCMED_
 1  TNG        WSPRODC  ___                  STCCR___    RCTLREG_
 1  TNG        WSPRODS  ___                  STCSR___    RSRVREG_
 1  TNG        WST*     ___                  STCWSTST    RWSTST__

  • Capturing a RMF workload activity report