The WEBWRA file is derived from SMF type 120 subtype 09 records. Each record contains ten triplet sections (v7) or 11 triplet sections (v8) with platform and z/OS specific details for every web request. Each observation in the MICS file contains complete details for the web request activity. The WEBWRA file interfaces with Accounting and Chargeback to support charging for CPU consumption and network I/O if desired. Understanding the WEBWRA File CPU Time Data Elements ---------------------------------------------------- The following discussion explains how the WEBWRA file CPU time measurements are calculated from the various raw metrics found in the SMF type 120 subtype 9 record. The raw metrics include values that are redundant, contain a combination of normalized and unnormalized values, and in the case of requests where enclaves are re-used, contain values that include CPU consumption from previous uses of the enclave. Most data elements in the WEBWRA file are named WRAxx, 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 WEBWRA file data element name --------------- ----------------------------- SMF1209BG WRABG SMF1209BH WRABH -and so on. This convention allows users familiar with the SMF type 120 subtype 9 record metrics to easily identify the corresponding CA MICS WEBWRA file data elements. The raw data CPU time related metrics found in the SMF type 120 record are kept in the WEBWRA file, using the same convention shown above, but additional, more traditionally named CPU time related data elements are added that simplify CPU resource use analysis and chargeback. These additional data elements are listed below: WRACPUTM - CP CPU Time WRAXCSTM - CP CPU Time Without zAAP/zIIP Eligible WRASUPTM - zIIP CPU Time WRASPNTM - Normalized zIIP CPU Time WRASUCTM - zIIP Eligible CPU Time on CP WRAZAPTM - zAAP CPU Time WRAZPNTM - Normalized zAAP CPU Time WRAZACTM - zAAP Eligible CPU Time on CP
The CA MICS WEBWRA file data elements previously listed 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 3 different IBM Macro calls, TIMEUSED, IWMEQTME, and IWM4EDEL. The values returned from the macro calls might or might not be populated. For example, if the enclave servicing the just-completed request is immediately re-used by a different request, the values returned by the IWM4EDEL macro contain zeros. And in this same multi-use enclave scenario, the values returned by the IWMEQTME macro are cumulative as each request re-uses the same enclave: --Obtained by WebSphere using the-- --Obtained by WebSphere using the-- --Obtained by WebSphere using the-- TIMEUSED Macro IWMEQTME Macro IWM4EDEL Macro IBM Metric CA MICS IBM Metric CA MICS IBM Metric CA MICS Name Name Description Name Name Description Name Name Description --------- ------- -------------- --------- ------- -------------- --------- ------- -------------- SMF1209CI (WRACI) - Total CPU Time SMF1209DA (WRADA) - Total CPU Time SMF1209DH (WRADH) - Total CPU Time SMF1209DB (WRADB) - zAAP CPU Time SMF1209DI (WRADI) - zAAP CPU Time SMF1209CX (WRACX) - Specialty Eng SMF1209DC (WRADC) - zAAP Time on CP SMF1209DK (WRADK) - zIIP CPU Time CPU Time SMF1209DD (WRADD) - zIIP Time on CP SMF1209DE (WRADE) - zIIP Eligible (Note 3) SMF1209DF (WRADF) - zIIP CPU Time SMF1209DG (WRADG) - zAAP Factor Normalization For requests where the enclave was used once, and then deleted, the CPU time metrics are populated from the values returned by the IWM4EDEL macro as follows: WRACPUTM - CP CPU Time = WRADH - (WRADI + WRADK) ; WRAXCSTM - CP CPU Time Without zAAP/zIIP Eligible = WRACPUTM - (WRADD + WRADC) ; WRASUPTM - zIIP CPU Time = WRADK / WRADG ; (Note 1) WRASPNTM - Normalized zIIP CPU Time = WRADK ; WRASUCTM - zIIP Eligible CPU Time on CP = WRADD / WRADG ; (Note 1) WRAZAPTM - zAAP CPU Time = WRADI ; WRAZPNTM - Normalized zAAP CPU Time = WRADI * WRADG ; (Note 2) WRAZACTM - zAAP Eligible CPU Time on CP = WRADC / WRADG ; (Note 2) For requests where the enclave was used multiple times, the process involved in determining CPU time values is complicated. In these cases, the values associated with the IWME4DEL macro contain zeros, except for the final use of the enclave, so for requests 1 through n-1 in a multi-use enclave scenario, the values returned by the IWMEQTME macro are used. For the final use of the enclave, the values returned by the IWME4DEL macro are populated, and are used for the CP, zIIP, and zAAP CPU time derivations. An additional complication arises because the values returned by the IWMEQTME macro are cumulative over each use of the enclave. For the first use of an enclave, the raw metrics represent the actual CPU usage. For subsequent requests using the same enclave, however, the metric values from the previous request are subtracted from the values in the current request record to determine the CPU time used by the current request. This delta processing is performed during raw data read-up, and the delta results are stored in the following data elements: WRADA2 - Total CPU Time Delta WRADB2 - zAAP CPU Time Delta WRADC2 - zAAP Time on CP Delta WRADD2 - zIIP Time on CP Delta WRADE2 - zIIP Eligible Delta (Note 3) WRADF2 - zIIP CPU Time Delta $SPAG After the correct CPU time values are determined for SMF type 120 records involving multiple uses of an enclave, the following formulas are used to populate the CPU time related data elements as shown below: WRACPUTM - CP CPU Time = WRADA2 - (WRADB2 + WRADF2) ; WRAXCSTM - CP CPU Time Without zAAP/zIIP Eligible = WRACPUTM - (WRADD2 + WRADC2) ; WRASUPTM - zIIP CPU Time = WRADF2 / WRADG; (Note 1) WRASPNTM - Normalized zIIP CPU Time = WRADF2; WRASUCTM - zIIP Eligible CPU Time on CP = WRADD2 / WRADG; (Note 1) WRAZAPTM - zAAP CPU Time = WRADB2; WRAZPNTM - Normalized zAAP CPU Time = WRADB2 * WRADG; (Note 2) WRAZACTM - zAAP Eligible CPU Time on CP = WRADC2 / WRADG; (Note 2) Note 1: zIIP CPU times, as recorded in the SMF type 120 subtype 9 record are normalized. To determine actual zIIP processor CPU time, the normalized value must be divided by the specialty engine normalization factor. The factor provided in the raw data is for zAAP processors, but in current IBM mainframe design, zAAP and zIIP processors always run at the same cycle speed, so the zAAP normalization factor is also the zIIP normalization factor. Note 2: zAAP CPU times, as recorded in the SMF type 120 subtype 9 record are not normalized. To determine normalized zAAP processor CPU time, the zAAP CPU time value must be multiplied by the zAAP engine normalization factor. Note 3: SMF type 120 subtype 9 records consistently record binary zeros in raw data field SMF1209DE, corresponding to CA MICS data elements WRADE and WRADE2, which should show the zIIP processor eligible CPU time.
|
Copyright © 2014 CA.
All rights reserved.
|
|