2. SAMPLE PLANNING APPLICATIONS › 2.12 WebSphere MQSeries Planning › 2.12.2 Control Parameters
2.12.2 Control Parameters
Relatively few parameters are needed to implement the
WEBSphere MQSeries Planning Sample Application. The control
screens included in the online facility allow you to quickly
enter the required information.
/----------------------- WebSphere MQSeries Planning ---------------------------\
|Command ===> |
|Enter a ? in any data entry field for more information on valid values. |
|Composing CAP DB File def.: MQ1 - WebSphere MQSeries Planning Sample Appl. |
| |
|Summarization Level |
| Primary ===> MONTHS (DAYS/WEEKS/MONTHS) |
| Secondary ===> ZONE (ZONE/HOUR/DAYNAME) |
| |
|Input File Time-Span ===> MONTHS (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) |
| |
|database ID (s) ===> ___________________________ |
| |
|MQSeries Workload Definition (CAPAPU) ===> MQMSSI (MQMSSI/NONE/EXIT) |
| Application unit title ===> ___________________________________ |
| |
|Specify extended options ===> N (Y/N) |
\------------------------------------------------------------------------------/
Figure 2-12.01. MQSeries Planning Screen
Figure 2-12.01 shows the MQSeries Planning screen, which is
the main control screen for the WebSphere MQSeries 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 MQAMMA 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 The number of cycles or versions of the
cycle: historical 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 The 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 MQAMMA file to be used
with this Sample application. If you are not
sure where the MQAMMA file resides, type a
question mark (?) in this field to display a
listing of the valid database units for this
Sample application.
MQSeries The three options for defining workload groups
Workload (see section 2.12.1, Usage Guidelines).
Definition
(CAPAPU):
Application The 1- to 40-character long name for the CAPAPU
unit title: data element. Use this parameter to describe
your workload groupings This parameter is only
available if you specify EXIT for the MQSeries
workload definition (CAPAPU) parameter.
Specify If you want extended options, enter Y (YES), and
extended the Extended Options Menu (Figure 2-12.02) is
options: displayed.
/--------------------------- Extended Options Menu ---------------------------\
|Command ===> |
| |
|Inquiry Step: WebSphere MQSeries 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) |
| CAPAPU derivation SAS statements ===> N (Y/N/R) |
| Notes report enabled ===> YES (YES/NO) |
| Contents reports enabled ===> YES (YES/NO) |
| |
| |
| |
| |
| |
\------------------------------------------------------------------------------/
Figure 2-12.02. MQSeries Planning Extended Options Menu
The extended options available with the WebSphere MQSeries
Planning Sample Application (Figure 2-12.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, hours or daynames
common data to be used for data selection from the CA MICS
selection input file(s). Enter Y (YES) to display the
parameters: Common Data Selection screen (Figure 2-12.03).
Enter R (RESET) to reset any selections you
previously made to SYSID and zone, hour or
dayname.
Specify You can use your own SAS statements to select
global data data from the CA MICS input file(s). Enter Y
selection (YES) to display the SAS System Statements
screen (Figure 2-12.04). Enter R (RESET) to
reset any selections you previously made to the
default of no user-specified data selection.
Specify You can use your own SAS statements for defining
CAPAPU your MQSeries workloads. Enter Y (YES) to
derivation display the SAS System Statements screen. Enter
SAS R (RESET) to reset any SAS SYSTEM STATEMENTs you
statements: previously made to a user-specified workload
grouping. This option is available only if you
specify EXIT for the MQSeries Workload
Definition (CAPAPU) parameter on the MQSeries
Planning screen.
Notes A Yes in this field prints any notes associated
report with the capacity planning file definition as
enabled: part of file updating.
Contents A Yes in this field prints the contents of the
reports capacity planning database file as part of file
enabled: updating.
/--------------------------- Common Data Selection ---------------------------\
|Command ===> |
| |
|Inquiry Step: Workload Planning Sample Application |
| |
| |
|SYSID ===> ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ |
| ____ ____ ____ ____ ____ |
| |
|Zone ===> _ _ _ _ _ _ _ _ _ (1 - 9) |
| |
|Hour ===> __ - __ __ - __ __ - __ __ - __ __ - __ (0 - 23) |
| |
|Dayname===> _________ _________ _________ _________ _________ |
| |
| |
| |
| |
| |
| |
| |
| |
| |
\------------------------------------------------------------------------------/
Figure 2-12.03. Common Data Selection Screen - MQSeries Planning
The Common Data Selection screen (Figure 2-12.03) allows 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: The specification for up to nine zones to be
included in the capacity planning database file.
Leave this parameter blank to include data for
all zones.
Hour: Specify the five hours or hour ranges to be
included in the capacity planning database file.
Selection of this parameter is valid only if you
specify the DETAIL, DAYS, or WEEKS timespan on
the MQSeries Planning screen (Figure 2-12.01).
Leave this parameter blank to include data for
all hours.
Dayname: Specify up to five daynames to be included 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-12.04. SAS System Statements Screen - MQSeries Planning Global Data
The SAS System Statements screen (Figure 2-12.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 provided and are field
protected from modification.
Note: This is a PDF/EDIT screen. All the PDF/EDIT commands
are available.
Copyright © 2014 CA.
All rights reserved.
|
|