2. SAMPLE PLANNING APPLICATIONS › 2.2 WLM Workload Planning › 2.2.4 WLM Workload Planning Example
2.2.4 WLM Workload Planning Example
You can use the WLM Workload Planning Sample Application to
build a Capacity Planning database file to track workload
activity and resource consumption as reported by the CA MICS
Hardware and SCP Analyzer.
Figures 2-2.08 through 2-2.12 show sample parameter
specifications for a WLM Workload Planning Sample
Application.
/----------------------------- WLM Workload Planning --------------------------\
|Command ===> |
|Enter a ? in any data entry field for more information on valid values. |
|Composing CAP DB File def.: GM1 - WLM Workload Planning Sample Application |
| |
|Summarization Level |
| Primary ===> MONTHS (DAYS/WEEKS/MONTHS) |
| Secondary ===> ZONE (ZONE/HOUR/DAYNAME) |
| |
|Input File Time-Span ===> DAYS (DETAIL/DAYS/WEEKS/MONTHS) |
| |
|Amount of data retained ===> 60 (1-9999 months) |
|Age of oldest forecast ===> 24 (1-9999 months) |
|History cycles ===> 3 (1-99 cycles) |
|Forecast cycles ===> 3 (1-99 cycles) |
| |
|Data base ID (s) ===> P |
| |
| |
|Specify extended options ===> Y (Y/N) |
| |
\------------------------------------------------------------------------------/
Figure 2-2.08. WLM Workload Planning Screen - Example
In Figure 2-2.08, the primary summarization level parameter
specifies that the application is to be summarized to using
the MONTHS timespan. The Summary level parameter specifies
that the data will be summarized in the ZONE level. The
DETAIL timespan will be used as input. The P specified for
the Database parameter indicates that the CA MICS WLMSEC and
WLMSEM files are located in a database unit that carries an
identifier of P.
In this example neither SYSIDs nor zones are aggregated into
composites.
The information specified for the Maximum amount of data
available for analysis and the Age of oldest forecast
parameters indicates that historical data up to 60 months old
and forecasts up to 24 months old are available for analysis.
The History and Forecast parameters specify that three cycles
of data will be retained.
The extended options should be requested to specify the
Workload Mapping Table or CAPAPU exit at a minimum.
/--------------------------- Extended Options Menu ---------------------------\
|Command ===> |
| |
|Inquiry Step: WLM Workload Planning Sample Application |
| |
| |
|Combine all SYSIDs into a composite ===> N (Y/N) |
| Composite SYSID ===> ____ |
| |
|Combine all zones into a composite ===> N (Y/N) |
| Composite zone ===> _________ |
| |
|Specify: |
| Common data selection parameters ===> Y (Y/N/R) |
| Global data selection exit ===> N (Y/N/R) |
| Workload mapping definition ===> Y (Y/N/R) |
| Workload mapping (CAPAPU) exit ===> N (Y/N/R) |
| CPU time adjustment parameters ===> Y (Y/N/R) |
| Notes report enabled ===> YES (YES/NO) |
| Contents reports enabled ===> YES (YES/NO) |
| |
| |
| |
\------------------------------------------------------------------------------/
Figure 2-2.09. Extended Options Menu - Example
On the Extended Options Menu shown in Figure 2-2.09, the
Specify common data selection, Specify CPU time adjustment,
and Specify workload mapping definition options are selected.
/--------------------------- Common Data Selection ---------------------------\
|Command ===> |
| |
|Inquiry Step: WLM Workload Planning Sample Application |
| |
| |
|SYSID ===> SYS1 SYS2 SYS3 ____ ____ ____ ____ ____ ____ ____ |
| ____ ____ ____ ____ ____ |
| |
|Zone ===> 1 2 3 4 _ _ _ _ _ (1 - 9) |
| |
|Hour ===> __ - __ __ - __ __ - __ __ - __ __ - __ (0 - 23) |
| |
|Dayname===> _________ _________ _________ _________ _________ |
| |
| |
| |
| |
| |
| |
| |
| |
| |
\------------------------------------------------------------------------------/
Figure 2-2.10. Common Data Selection Screen - Example
In Figure 2-2.10, the SYSIDs SYS1, SYS2 and SYS3 are selected
for inclusion in the generated database files. Zones 1, 2,
3, and 4 will also be included. Data for all hours will be
generated.
/----------------- CPU Time Adjustment Parameters -------------------------\
|Command ===> |
| |
|Inquiry step: WLM Workload Planning Sample Application |
| |
| |
|Base CPU model ===> 3081-KX |
|Number of processors in base CPU model ===> 2 (1-16) |
|Base CPU service unit coefficient ===> 396.4 (per processor) |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
\------------------------------------------------------------------------------/
Figure 2-2.11. CPU Time Adjustment Parameters Screen - Example
Figure 2-2.11 shows that an IBM 3081-KX processor is chosen
as the base CPU model for this example. The number of
internal processors and the service-unit-to-CPU-second factor
are determined from vendor information on the processor.
/---------------------- Workload Mapping Definition --------------------------\
|Command ===> |
| |
|Inquiry step: WLM Workload Planning Sample Application |
| |
| |
|Workload mapping table data set name |
| ===> MYWKLMAP.DATA |
| |
| |
| Edit workload mapping table ===> NO (YES/NO) |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
\------------------------------------------------------------------------------/
Figure 2-2.12. WLM Workload Mapping Definition Screen - Example
In Figure 2-2.12 a workload mapping table is built externally
using the ISPF Editor. The data set name of the volume
mapping table is specified as MYWKLMAP.DATA.
Copyright © 2014 CA.
All rights reserved.
|
|