2. SAMPLE PLANNING APPLICATIONS › 2.3 WLC Implementation Planning › 2.3.2 Control Parameters
2.3.2 Control Parameters
Relatively few parameters are needed to implement the WLC
Implementation Planning Sample Application. The control
screens included in the online facility allow you to quickly
enter the required information.
/--------------------WLC Implementation Planner--------------------------------\
|Command ===> |
|Enter a ? in any data entry field for more information on valid values. |
|Composing CAP DB File def.: WLC - WLC Implementation Planning |
| |
|Summarization Level |
| Primary ===> MONTHS (DAYS/WEEKS/MONTHS) |
| Secondary ===> ZONE (ZONE/HOUR/DAYNAME) |
| |
|Input File Time-Span ===> DETAIL (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) ===> ___________________________ |
| |
| |
| |
|Specify extended options ===> Y (Y/N) |
\------------------------------------------------------------------------------/
Figure 2-3.01. WLC Planning Control Screen
Figure 2-3.01 shows the WLC Planning screen, which is the
main control screen for the WLC Implementation Planning
Sample Application. It contains the following fields:
Summariza- The output summarization corresponds to the
tion level: combination of the primary and secondary
summarization levels. These control how the
output file is summarized in your capacity
planning database.
Input file The timespan (either DETAIL, DAYS, WEEKS or
timespan: MONTHS) of the HARCPU and HARLPU Files that
you want to use as input when creating the
capacity planning database file.
Amount of The number of days, weeks or months of
data historical data to be retained in the CAPxxx01
retained: cycle of the capacity planning database file.
Any historical observations older than what you
specify for this parameter are dropped from the
file during the file update.
Age of The number of days, weeks or months that you
oldest want to retain a forecast after it is generated.
forecast: Any forecast older than what you specify for
this parameter is dropped when a new forecast is
generated and saved.
History Number of cycles or versions of the historical
cycle: data you want to retain. A new cycle is created
when the file is updated and the existing cycles
aged (for example, Cycle 01 is aged to Cycle 02
and Cycle 02 becomes Cycle 03).
Forecast Number of cycles or versions of the forecast
cycle: data you want to retain. A new cycle is created
when you specify forecast aging in one of the
workload forecasting routines and the existing
cycles are aged (for example, Cycle 01 is aged
to Cycle 02 and Cycle 02 becomes Cycle 03).
Database The database unit identifier(s) (up to fourteen
ID(s): units) that contain the HARCPU and HARLPU
Files to be used with this Sample
application. If you are uncertain in which
database unit the HARCPU and HARLPU
Files reside, type a question mark (?) in this
field to display a message listing of the valid
database unit identifiers for this Sample
application.
Specify If you want extended options, enter Y (YES), and
extended the Extended Options Menu (Figure 2-3.02) is
options: displayed.
/--------------------------- Extended Options Menu ---------------------------\
|Command ===> |
| |
|Inquiry Step: WLC Implementation 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 ===> N (Y/N/R) |
| Global data selection exit ===> N (Y/N/R) |
| CPU time adjustment parameters ===> N (Y/N/R) |
| Notes report enabled ===> YES (YES/NO) |
| Contents reports enabled ===> YES (YES/NO) |
| |
| |
| |
| |
| |
\------------------------------------------------------------------------------/
Figure 2-3.02. WLC Planning Extended Options Menu
The extended options available with the WLC Implementation
Planning Sample Application (Figure 2-3.02) are:
Combine all You can combine SYSIDs in the capacity planning
SYSIDs into database file. Enter Y (YES) if you want data
a composite: for all of the SYSIDs to be summarized into a
single observation with the composite SYSID
value.
Combine all You can combine zones, hours, and daynames in
zones/hours/ the capacity planning database file. The prompt
daynames for this field changes to zones or hours or
into a daynames depending on what you specify for the
composite: summary level parameter. Enter Y (YES) if you
want all of the zones, hours, and daynames to be
summarized into a single observation with the
composite value.
Specify Specify the SYSIDs and zones, and data hours or
common data daynames to be used for data selection from the
selection CA MICS input file(s). Enter Y (YES) to display
parameters: the Common Data Selection screen (Figure
2-3.03). Enter R (RESET) to reset any
specifications you previously made to SYSID and
zone, hour or dayname.
Specify You can use your own SAS statements to select
global data data from CA MICS file(s). Enter Y (YES) to
selection display the SAS System Statements screen (Figure
exit: 2-3.04). Enter R (RESET) to reset any
selections you previously made to the default of
no user-specified data selection.
Specify Specify the parameters to use for CPU time
CPU time adjustment (normalization). Enter Y (YES) to
adjustment display the CPU Time Adjustment Parameters
parameters: screen (Figure 2-3.03). Enter R (RESET) to
reset any selections you previously made to CPU
time adjustment.
This option is not available if you select the
composite SYSID option on this screen.
Notes If you have entered notes associated with the
reports capacity planning database file definition, a
enabled: Yes in this field prints the note as part of
file updating.
Contents A Yes in this field prints the contents of the
reports capacity planning file as part of file updating.
enabled:
/--------------------------- Common Data Selection ---------------------------\
|Command ===> |
| |
|Inquiry Step: WLC Implementation Planning Sample Application |
| |
| |
|SYSID ===> ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ |
| ____ ____ ____ ____ ____ |
| |
|Zone ===> _ _ _ _ _ _ _ _ _ (1 - 9) |
| |
|Hour ===> __ - __ __ - __ __ - __ __ - __ __ - __ (0 - 23) |
| |
|Dayname===> _________ _________ _________ _________ _________ |
| |
| |
| |
| |
| |
| |
| |
| |
| |
\------------------------------------------------------------------------------/
Figure 2-3.03. Common Data Selection Screen - WLC Planning
The Common Data Selection screen (Figure 2-3.03) lets you to
define the following data selection criteria:
SYSID: The SYSIDs that you want to include in your
capacity planning database file. You can
specify a maximum of 15 one- to four-character
SYSIDs. Leave this parameter blank to include
data for all SYSIDs.
Zone: You can specify up to nine zones to include in
the capacity planning database file. Leave this
parameter blank to include data for all zones.
Hour: Specify up to five hours or hour ranges to
include in the capacity planning database file.
Selection of this parameter is valid only if you
enter the DETAIL, DAYS, or WEEKS timespan on the
WLC Planning screen (Figure 2-3.03). Leave this
parameter blank to include data for all hours.
Singular hour values must be entered to the left
of the dash.
Dayname: You can enter up to five daynames to include in
the capacity planning database file. Leave
blank to include all days. Input the first
unique characters and the application will fill
in the rest. Selection of this parameter is only
valid when the input timespan is DETAIL or DAYS.
/-------------------------- SAS System Statements ---------- COLUMNS 001 072--\
|Command ===> Scroll ===> PAGE |
| |
|SAS Statements for the SELECT Macro |
|-------------------------------------------------------------------------------|
|****** ***************************** TOP OF DATA ******************************|
|==MSG> SPECIFY SAS STATEMENTS TO SUBSET THE CAPACITY PLANNING DATA BASE FILE. |
|=NOTE= %MACRO SELECT; <=== PLEASE DO NOT PLACE LINES BEFORE THIS LINE. |
|000001 |
|000002 |
|000003 |
|000004 |
|000005 |
|000006 |
|000007 |
|000008 |
|000009 |
|000010 |
|=NOTE= %MEND SELECT; <=== PLEASE DO NOT PLACE LINES AFTER THIS LINE. |
|****** **************************** BOTTOM OF DATA ****************************|
| |
\------------------------------------------------------------------------------/
Figure 2-3.04. SAS System Statements Screen - WLC Planning Global Data Selection
The SAS System Statements screen (Figure 2-3.04) lets you
define your own data selection logic. You can code any valid
SAS statements as described in the SAS manuals. The %MACRO
SELECT and %MEND SELECT statements are already provided, and
are field protected from modification.
Note: This is a PDF/EDIT screen. All PDF/EDIT commands are
available.
/----------------------- CPU Time Adjustment Parameters ----------------------\
|Command ===> |
| |
|Inquiry step: IRD Implementation 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-3.05. CPU Time Adjustment Parameters Screen
The information on the CPU Time Adjustment Parameters screen,
shown in Figure 2-3.05, is required only if you choose CPU
time normalization for the IRD Implementation Planning Sample
Application.
Base CPU The 10-character identifier for the base
model: processor. Any name is acceptable in this
field. Do not use embedded blanks or equal
signs (=) in this value. For example, if you
wish to normalize your actual CPU time values to
the equivalent of a 3081-KX, then code 3081-KX
in this field.
Number of The number of internal CPUs in the base
processors processor. This value must be an integer (that
in base CPU is, do not use a decimal point), and it must be
model: greater than 0 and less than or equal to 16.
For example, if you specify a 3081-K as the base
CPU model, then code a 2 in this field since a
3081-K has two internal CPUs.
Base CPU The service-units-to-CPU-seconds conversion
service factor for the base processor. The value must
unit be a real number greater than 0. You can
coefficient: compute a relative performance rating by
dividing this value by the corresponding
service-unit-to-CPU-second factor for the
processor represented by the SYSID (see Section
2.1.1 for an example of this calculation). You
may want to use vendor-supplied values for the
factor, or a factor based on your own
evaluations. For example, if you specify a
3081-K as the base CPU model, then code 396.4 in
this field.
Copyright © 2014 CA.
All rights reserved.
|
|