Screen Operation - File Definition
Create user-defined resource element files.
micsrm140
The following Figure 3-7 shows the first step for creating a user-defined resource element file.
Figure 3-7. Resource Element File Definition Screen
/---------------------- Resource Element File Definition ---------------------\ |Command ===> | |Enter a ? in any data entry field for more information on valid values. | | CAP DB File def.: SYS - System Activity Tracking File | | | |Summarization Level | | Primary ===> MONTHS (DAYS/WEEKS/MONTHS) | | Secondary ===> ZONE (ZONE/HOUR/ENDTS/DAYNAME) | | | |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) | | | |Enable: | | Notes report ===> N (YES/NO) | | Contents reports ===> N (YES/NO) | | | |Specify extended options ===> Y (Y/N) | --------------------------------------------------------------------------------
The Resource Element File Definition screen that is shown in Figure 3-7 is the main control screen for defining resource element files. It contains the following fields:
Summarization level
The output summarization corresponds to the combination of the primary and secondary summarization levels. These levels control how the output file is summarized in your capacity planning database.
Note:
When you choose a secondary summarization level of ENDTS, you can only select one MICS
file as input. This is due to the difficulty in merging ENDTS values across multiple files.Amount of data retained
The number of days, weeks or months of historical data to be retained in the CAPxxx01 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 oldest forecast
The number of days, weeks or months that you want to retain a forecast after it is generated. Any forecast older than what you specify for this parameter is dropped when a new forecast is generated and saved.
History cycle
Number of cycles or versions of the 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 cycle
Number of cycles or versions of the forecast 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).
Notes report enabled:
If you have entered notes associated with the capacity planning database file definition, a Yes in this field prints the note as part of file updating.
Contents reports enabled:
A Yes in this field prints the contents of the capacity planning file as part of file updating.
Specify Extended Options
The specification for selecting extended options. If you specify Y (YES), the Extended Options Menu shown in Figure 3-8 displays.
Figure 3-8. Resource Element Extended Options Menu
/--------------------------- Extended Options Menu ---------------------------\ |Command ===> | | | |Inquiry Step: | | | |Combine SYSIDs into a composite ===> N (Y/N) | | Composite SYSID ===> ____ | |Combine zones into a composite ===> N (Y/N) | | Composite zone ===> _________ | | | |Number of CAPAPUS ===> 0 (0 through 9) | |CAPAPU title (First APU) ===> ________________________________________ | |CAPAPU2 title ===> ________________________________________ | |CAPAPU3 title ===> ________________________________________ | |CAPAPU4 title ===> ________________________________________ | |CAPAPU5 title ===> ________________________________________ | |CAPAPU6 title ===> ________________________________________ | |CAPAPU7 title ===> ________________________________________ | |CAPAPU8 title ===> ________________________________________ | |CAPAPU9 title ===> ________________________________________ | | | |Specify | | SAS Statements to set CAPAPUs ===> N (Y/N/R) | | | --------------------------------------------------------------------------------
Combine all SYSIDs into a composite
You can combine SYSIDs in the capacity planning database file. Enter Y (YES) if you want data for all of the SYSIDs to be summarized into a single observation with the composite SYSID value. Figure 3-28 illustrates specifying SYSIDs for inclusion in the database.
Combine all zones/hours/daynames into a composite
You can combine zones, hours, and daynames in the capacity planning database file. The prompt for this field changes to zones or hours or daynames depending on what you specify for the 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 zone/hour/dayname value. Figure 3-28 illustrates specifying zones/hours for inclusion in the database.
Number of CAPAPUs
Specify the number (0 to 9) of application units: (CAPAPUs) you are defining for this file. This activates the optional CAPAPU feature so that these data elements are present in the Capacity Planning database file, and are included in the summarization sequence during file summarization and merging. If you specify that CAPAPUs are to be active, you will be prompted to specify the SAS statements needed to derive the CAPAPU groupings and corresponding CAPAPU values.
CAPAPU titles
Specify the 1-40 character title for each CAPAPU titles: you are defining for this data element.
Specify SAS Statements to set CAPAPUs
The specification that allows you to use your own SAS Statements for defining your resource element file. Specify Y (YES) to display the: SAS Statements screen that is shown in Figure 3-9. This option is only available if you specify CAPAPUs.
Figure 3-9. SAS Statements Screen - Defining CAPAPU
/------------------------ SAS System Statements ------------------------------\ |Command ===> Scroll ===> CSR | | | |SAS Statements for the CAPAURT Macro | |-------------------------------------------------------------------------------| |****** ***************************** TOP OF DATA ******************************| |==MSG> SPECIFY SAS STATEMENTS TO SET CAPAPU VALUES. | |=NOTE= %MACRO CAPAURT; <=== PLEASE DO NOT PLACE LINES BEFORE THIS LINE. | |000001 | |000002 | |000003 | |000004 | |000005 | |000006 | |000007 | |000008 | |000009 | |000010 | |=NOTE= %MEND CAPAURT; <=== PLEASE DO NOT PLACE LINES AFTER THIS LINE. | |****** **************************** BOTTOM OF DATA ****************************| --------------------------------------------------------------------------------
The SAS Statements screen that is shown in Figure 3-9 allows you to define the SAS statements that are required to group
MICS
input observations into application workload groups that are appropriate for your installation. All statements that you specify must conform with the syntax specified in the SAS manuals. The CAPAPU(s) value is a maximum of 64 characters.Note that the %MACRO CAPAURT and %MEND CAPAURT statements are provided for you and that they are field-protected from modification.
A special data element, CAPIFILE, is available to you for use in defining your CAPAPU values. This three-character data element contains the
MICS
file suffix that corresponds to the MICS
file that you choose for processing after you select the Insert MICS
File and Data Element Selection option on the Resource Element File menu (see the Element Selection section). For example, if you specify the Insert File and Data Element Selection option twice, once for the SCPPGA File and again for the SCPPPA File, the value of CAPIFILE will be PGA during the processing of the SCPPGA File and PPA during the processing of the SCPPPA File. The following example illustrates the use of the CAPIFILE data element in defining CAPAPU values.You can rewrite the Performance Group/Period Workload Tracking example in the Performance Group/Period Workload Tracking section to use the CAPAPU feature by defining the following statements in the CAPAPU exit:
%MACRO CAPAURT; IF CAPIFILE EQ 'PPA' AND PERFGRP EQ 2 THEN DO; IF PERFPER EQ 1 THEN CAPAPU='WORKLOAD1'; ELSE IF PERFPER EQ 2 THEN CAPAPU='WORKLOAD2'; ELSE IF PERFPER EQ 3 THEN CAPAPU='WORKLOAD3'; ELSE IF PERFPER EQ 4 THEN CAPAPU='WORKLOAD4'; ELSE IF PERFPER EQ 5 THEN CAPAPU='WORKLOAD5'; END; ELSE IF CAPIFILE EQ 'PGA' THEN DO; IF PERFGRP EQ 7 THEN CAPAPU='WORKLOAD6'; ELSE IF PERFGRP EQ 62 THEN CAPAPU='WORKLOAD7'; ELSE IF PERFGRP NE 2 THEN CAPAPU='WORKLOAD8'; END; %MEND CAPAURT;