3. IMPLEMENTATION › 3.7 Avoiding SNT Duplicate Charging › 3.7.1 Avoiding Web Duplicate Charging

3.7.1 Avoiding Web Duplicate Charging

 
 With the Web Analyzer, duplicate charging can occur by
 billing the same unit of work from both the Server Access Log
 (SAL) and Server Activity File (SAF) journal files.
 
 The Rate Table ISPF dialogs prevent duplicate charging across
 Web Analyzer files by not allowing you to activate both the
 SAL (ACTJWB) and the SAF (ACTJSF) Journal Files if the same
 units of work are being charged in each.
 
 
 AVOIDING DUPLICATE CPU TIME CHARGES IN AN ENVIRONMENT WITH
 SPECIAL PROCESSORS
 
 There are two types of IBM special processors, zSeries
 Application Assist Processors (zAAPs) and z9 Integrated
 Information Processors (zIIPs).
 
 For address spaces, the portion of CPU time spent by an
 address space executing on a special processor is kept
 separate from the portion of CPU time that is spent by the
 same address space while it executed on a standard
 processor.  The CA MICS data elements that contain the
 special processor CPU times are the following:
 
  WRAZPNTM - Normalized zAAP CPU Time
  WRASPNTM - Normalized zIIP CPU Time
 
 The CPU time spent by an address space that could have
 executed on a special processor, but executed on a standard
 CP because a special processor was not available, is
 considered special processor eligible CPU time.  Special
 processor eligible CPU time is a subset of CP CPU Time
 (WRACPUTM). The CA MICS data elements that contain special
 processor eligible CPU time are the following:
 
  WARZACTM - zAAP Eligible CPU Time on a CP
  WARSUCTM - zIIP Eligible CPU Time on a CP
 
 
 There is a potential for duplicate charging for special
 processor eligible CPU time if you want to use a different
 rate for eligible CPU time than that used for work that had
 to run on the standard processors.  It is important to
 understand, that if you charge for both special processor
 eligible CPU time and the total CP CPU time, you will be
 charging for the special processor eligible CPU time twice.
 
 If the desire is to charge the same rate for special
 processor eligible CPU time as CP CPU time, it is recommended
 you use the computation codes 3037  for WRACPUTM.
 
 
 If you want to charge a different rate for special processor
 eligible CPU time that ran on a CP processor, versus the
 portion of CP processor CPU time that had to execute on CP
 processors, use the following computation codes:
 
 o CP CPU Time that was Eligible to Run on Special Processors
 
 COMP
 CODE   Element    Label
 ----   --------   ------------------------------
 3035   WRAZACTM   zAAP Eligible CPU Time on a CP
 3032   WRASUCTM   zIIP Eligible CPU Time on a CP
 
 o CP CPU Time that was not Eligible to Run on Special
   Processors
 
 COMP
 CODE   Element    Label
 ----   --------   -----------------------------------
 3036   WRAXCSTM   CPU Time without zAAP/zIIP Eligible
 
 The computation of WRAXCSTM is:
 
   WRAXCSTM = WRACPUTM - (WRASUCTM + WRAZACTM)