For the CPC level chart, CPC level PR/SM data element values are substituted for the LPAR data elements:
ENGDISPT – Total zAAP Engine Dispatch (Set to PRSMTZST – Total zAAP Dispatch Time – Shared / 3600)
ENGDISPE – Effective zAAP Engine Dispatch (Set to PRSMTZET – Total zAAP Dispatch Time - Effective / 3600)
This vertical bars, for the CPC level LPAR ##CPC##, show the total and effective dispatch of the physical processors in the entire shared zAAP engine pool. For this chart, a user data step takes the following actions before the ENGDISPT and ENGDISPE derivations:
This process permits a CPC level view of the physical shared zAAP engine pool dispatch activity. The total and effective dispatch times are divided by 3600 to convert from seconds of dispatch to hours of dispatch. Since one engine can be dispatched a maximum of one hour, per hour, this conversion allows the dispatch of the engine pool to be represented as physical engine dispatch hour equivalents. For example, three zAAP engines could, at full utilization, provide three hours of dispatch time in one hour.
LPCAVZAP - Avg Number of Active zAAP Processors (Set to PRSMANSP – Avg zAAP Sharable Processors)
This horizontal reference line, for the CPC level LPAR ##CPC##, shows the average number of physical processors in the shared zAAP engine pool. While the data extract plots data element LPCAVZAP, which is the average number of logical CP engines assigned to an LPAR—for the ##CPC## chart, a user data step populates LPCAVZAP with the value for PRSMANSP—which is the average number of physical engines in the shared zAAP engine pool. The actual dispatch engine equivalents, charted with the vertical bars, can reach, but should never exceed this line. IBM features like capacity provisioning and on/off capacity on demand can activate and deactivate physical processors—so this line may not reflect a constant value over the entire day.
HOUR – Hour of Day
|
Copyright © 2014 CA.
All rights reserved.
|
|