The WEBWAA file contains the contents of the Asynchronous
data section in the SMF 120 subtype 9 records. This section
became available with Websphere Application Server version 8.
Most data elements in the WEBWAA file are named WAAxx, where
xx correlates to the raw data metric naming convention
adopted by IBM when designing the SMF type 120 subtype 9
record. For example:
IBM metric Name WEBWAA file data element name
--------------- -----------------------------
SMF1209GV WAAGV
SMF1209GW WAAGW
and so on.
This convention allows users familiar with the SMF type 120
subtype 9 record metrics to easily identify the corresponding
CA MICS WEBWAA file data elements.
A normal web request can spawn or create asynchronous work
that does not require a response back to the original web
requestor. Also, an asynchronous transaction can create
another asynchronous piece of work. A number of elements are
available to trace back to the execution context of the
creating web request, whether it is a normal web request, or
another asynchronous piece of work. If the asynchronous work
executed on the same enclave, use the common enclave token
date element (WEBCY) to identify the related web requests.
If the work was not done on the same enclave, use WAAHA to
match with WEBCY of the creating request. Several other
execution context elements are also available to help
identify the creating web request:
WAAHA - Execution Context Enclave Token
WAAGU - Execution Context Task ID
WAAGV - Execution Context TCB Address
WAAGW - Execution Context TCB TTOKEN
Understanding the WEBWAA File CPU Time Data Elements
----------------------------------------------------
The following discussion explains how the WEBWAA file CPU
time measurements are calculated from the various raw metrics
found in the SMF type 120 subtype 9 record Asynchronous data
section. The Asynchronous work can run on the same enclave
as the web request that submitted it, or from another
asynchronous request that submitted it. The CPU metrics
acquired from the IWMEQTME macro will contain accumulated CPU
time from the prior request using the same enclave. Due to
the disconnect between the web request and asynchronous
request, the CPU times acquired from the TIMEUSED macro,
which provide just the CPU time used for individual
asynchronous work are used. This includes CPU time on the CP
engine and CPU time on a specialty engine.
The raw data CPU time-related metrics found in the SMF type
120 record Asynchronous section are kept in the WEBWAA file,
using the convention previously described, but additional,
more traditionally named CPU time-related data elements are
added. These elements simplify CPU resource use analysis and
chargeback; they are listed below:
WAACPUTM - CP CPU Time
WAAAZZTM - zIIP/zAAP CPU Time
WAANZZTM - Normalized zIIP/zAAP CPU Time
The CA MICS WEBWAA file data elements listed previously are derived from the following raw CPU time related metrics found in the SMF type 120 subtype 9 record. These various CPU time related metrics are obtained by WebSphere issuing two different IBM Macro calls, TIMEUSED and IWMEQTME. The enclave CPU metrics from the IWMEQTME macro might contain CPU time from threads or processes. As a result, we rely solely on the CPU times from the TIMEUSED macro for Asynchronous work. --Obtained by WebSphere using the-- --Obtained by WebSphere using the-- TIMEUSED Macro IWMEQTME Macro IBM Metric CA MICS IBM Metric CA MICS Name Name Description Name Name Description --------- ------- -------------- --------- ------- -------------- SMF1209HN (WAAHO) - Total CPU Time SMF1209HG (WAAHG) - Total CPU Time SMF1209HH (WAAHH) - zAAP CPU Time SMF1209HO (WAAHO) - Specialty Eng SMF1209HI (WAAHI) - zAAP Time on CP CPU Time SMF1209HJ (WAAHJ) - zIIP Time on CP SMF1209HK (WAAHK) - zIIP Eligible SMF1209HL (WAAHL) - zIIP CPU Time SMF1209HM (WAAHM) - zAAP Factor Normalization
|
Copyright © 2014 CA.
All rights reserved.
|
|