Creating a Database Specification

Create user-defined resource element files.
micsrm140
The online screens that the
MICS Capacity Planner
uses to create user-defined resource element files are described in the following sections:
File Definition
The following figure 3-93 shows the first step for creating a user-defined meta file.
Figure 3-93. Meta File Definition Screen
/---------------------------- Meta File Definition ---------------------------\ |Command ===> | |Enter a ? in any data entry field for more information on valid values. | |Composing CAP DB File def.: SYS - System Activity Tracking File | | | |Summarization Level | | Primary ===> MONTHS (DETAIL/DAYS/WEEKS/MONTHS) | | Secondary ===> ZONE (ZONE/HOUR/ENDTS/DAYNAME) | | | |Capacity Planner Data Base ===> PRIVATE (Private/Shared) | | | |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 ===> YES (YES/NO) | | Contents reports ===> YES (YES/NO) | | | |Specify extended options ===> N (Y/N/R) | --------------------------------------------------------------------------------
The Meta File Definition screen shown in Figure 3-93 is the main control screen for defining meta 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 Planner 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.
Capacity Planner Database
The specification that tells where ALL input files that make up this Meta file reside. Choose
PRIVATE (the default) if you want the meta file to be made up of information in your own Capacity Planning database. Choose SHARED if you want to process information in the Shared Capacity Planning database.
Note:
If this meta file will ever be executed using the Production Updating Feature of
MICS
, this field must be set to SHARED, because you will not be able to copy the file definition from your private catalog to the shared catalog.
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 cycles
The number of cycles or versions of the historical data that you want to retain. A new cycle is created when the file is updated and the existing cycles are aged (that is, Cycle 01 becomes Cycle 02 and Cycle 02 becomes Cycle 03).
Forecast cycles
The number of cycles or versions of the forecast data that 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 (that is, Cycle 01 becomes Cycle 02 and Cycle 02 becomes Cycle 03).
Specify Extended Options
The specification for selecting extended options. If you specify Y (YES), the Extended Options Menu that is shown in Figure 3-94 displays.
Figure 3-94. Meta File 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 into a composite
The specification for combining SYSIDs in the Capacity Planning database file. Specify a Y (YES) if you want data for all of the SYSIDs to be summarized into a single observation with the Composite SYSID value.
Combine all zones/hours/daynames into a composite
The specification for combining zones/hours in the Capacity Planning database file. The prompt for this field changes to zones, hours or daynames depending on what you specify for the summary level parameter. Specify a Y (YES) if you want all of the zones/hours/daynames to be summarized into a single observation with the Composite zone/hour/dayname value.
Number of CAPAPUs
Specify the number (0 to 9) of application units (CAPAPUs) you are defining for this element. 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 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-95. This option is only available if you specify CAPAPUs.
Figure 3-95. 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-95 allows you to define the SAS statements that are required to group CAP 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.
Two special data elements are available to you for use in defining your CAPAPU values. The first, CAPIFILE, is a three-character data element that contains the CAP file name that corresponds to the CAP file that you chose for processing after you selected the Insert CAP File and Data Element Selection option on the Meta File menu (see the Element Selection below). The second, CAPIAPU (including CAPIAPU2 to CAPIAPU9), corresponds to the CAPAPU value found for the current observation being read from the input CAP file that you chose. For example, if you specify the Insert CAP File and Data Element Selection twice, once for CAP file: CPG, which has one observation for each Performance Group and again for CAP file
CPA, which has one observation for each Performance Group/Performance Period combination. CAPIFILE would be 'CPG' when reading the CPG file and 'CPA' when reading the CPA file. The following example illustrates the use of the CAPIFILE and CAPIAPU data elements in defining new CAPAPU values for the output meta file:
%MACRO CAPAURT; IF CAPIFILE EQ 'CPA' AND SUBSTR(CAPIAPU,1,1) EQ 2 THEN DO; IF SUBSTR(CAPIAPU,2,1) EQ 1 THEN CAPAPU='WORKLOAD1'; ELSE IF SUBSTR(CAPIAPU,2,1) EQ 2 THEN CAPAPU='WORKLOAD2'; ELSE IF SUBSTR(CAPIAPU,2,1) EQ 3 THEN CAPAPU='WORKLOAD3'; ELSE IF SUBSTR(CAPIAPU,2,1) EQ 4 THEN CAPAPU='WORKLOAD4'; ELSE IF SUBSTR(CAPIAPU,2,1) EQ 5 THEN CAPAPU='WORKLOAD5'; END; ELSE IF CAPIFILE EQ 'CGA' THEN DO; IF SUBSTR(CAPIAPU,1,1) EQ 7 THEN CAPAPU='WORKLOAD6'; ELSE IF SUBSTR(CAPIAPU,1,2) EQ 62 THEN CAPAPU='WORKLOAD7'; ELSE IF SUBSTR(CAPIAPU,1,1) NE 2 THEN CAPAPU='WORKLOAD8'; END; %MEND CAPAURT;
Element Selection
Figure 3-96, Meta File menu, shows the next step in creating a user-defined meta file definition.
Figure 3-96. Meta File Menu
/------------------------------- Meta File -----------------------------------\ |Option ===> | | | |Composing CAP DB file def.: SYS - System Activity Tracking File | | | | | | 1 - Insert Common Data Selection | | Specify data selection criteria to apply to ALL files. | | 2 - Insert CAP File and Data Element Selection | | Select a Capacity Planner file and data elements. | | 3 - Insert Cross-File Data Element Definition | | Specify cross-file data element derivations. | | | | | | | | | | | | | | | | | | | | | | | --------------------------------------------------------------------------------
After you complete specifying the meta file definition control parameters, you are ready to define the steps to build your Capacity Planning database file. (Refer to Figure 3-2 to see how these steps correspond to user specifications for the selection, summary, and merge phases of database creation.) The Meta File menu provides you with the opportunity to define selection criteria that you wish to apply to each CAP file that you define as an input data source for your meta file.
You may choose from the following options on the Meta File menu:
Insert Common Data Selection
Specify Option 1, Insert Common Data Selection, to specify the data selection criteria that you want to apply to every CAP file that provides input data in building your meta file. The Common Data Selection screen shown in Figure 3-97 is displayed.
You can specify only one common data selection step for each meta file. You must complete this before proceeding with the succeeding steps.
Insert CAP File and Data Element Selection
Specify Option 2, Insert CAP File and Data Element Selection, to define a CAP file and data element selection step for each CAP file that provides input data for your meta file. The CAP File and Data Element Selection screen shown in Figure 3-99 is displayed. (Both the file-unique selection and summary phases shown in Figure 3-100 occur during this step.) You may select this option more than once.
Using this screen and its associated exit screens, you can define the CAP data elements that will comprise your meta file, along with any file-unique data selection and/or summarization logic.
If you can to define any data elements that are derived from data elements from a single CAP file, you can usually specify the data element derivation SAS statements through one of the exit screens associated with this screen. If you are defining data elements that are derived from data elements from multiple CAP files, you can specify the data element derivation SAS statements in the cross-file data element definition step.
Insert Cross-File Data Element Definition
Specify Option 3, Insert Cross-File Data Element Definition, to define any data elements that you want to derive from data elements from multiple CAP files. The Cross-File Data Element Definition screen that is shown in Figure 3-102 is displayed. (This step corresponds to the merge phase shown in Figure 3-2.) Also specify the data element derivation SAS statements that will be used to derive these data elements.
Since the specifications associated with this step apply to the merging of data from multiple CAP files, you may specify a cross-file data element definition step only if you specify multiple CAP file and data element selection steps. In this case, the cross-file data element definition step is required to create a valid file definition inquiry.
Each time that you complete the specifications for an individual step, END from the screen to redisplay the Meta File Menu that is shown in Figure 3-104. You can then insert another step in your meta file definition. Repeat this process until you define all of the steps necessary to build your meta file.
The three options are further discussed in the following sections:
  • Insert Common Data Selection
  • Insert CAP File and Data Element Selection
  • Insert Cross-File Data Element Definition
Insert Common Data Selection
If you select Option 1, Insert Common Data Selection, on the Meta File menu, the Common Data Selection screen that is shown in Figure 3-97 is displayed.
Figure 3-97. Common Data Selection Screen
/--------------------------- Common Data Selection ---------------------------\ |Command ===> | |Enter a ? in any data entry field for more information on valid values. | |Composing CAP DB File def.: SYS - System Activity Tracking File | | | | | |SYSID ===> ____ ____ ____ ____ ____ ____ ____ ____ ____ ____ | | ____ ____ ____ ____ ____ | | | |Zone ===> _ _ _ _ _ _ _ _ _ (1 - 9) | | | |Hour ===> __ - __ __ - __ __ - __ __ - __ __ - __ (0 - 23) | | | |Dayname ===> _________ _________ _________ _________ _________ | | | | | | | | | | | | | | | | | |Specify common data selection SAS statements ===> N (Y/N/R) | --------------------------------------------------------------------------------
The data selection criteria that you specify using this screen is applied to each CAP file that provides input data in creating and updating your Capacity Planning database file.
The parameters for the Common Data Selection screen are defined below:
SYSID
The SYSIDs that you want to include in your Capacity Planning database file. You may specify a maximum of 15 one- to four-character SYSIDs. Leave this parameter blank to include data for all SYSIDs. The standard method is to create one record for each SYSID that is created for each day, week, or month processed. Alternatively, you can summarize multiple SYSIDs into a single record.
Zone
The zones that you want to include in your Capacity Planning database file. You may specify a maximum of nine one-character zones. Leave this parameter blank to include data for all zones. The standard method is to create one record for each zone that is created for each week or month processed. Alternatively, you may wish to summarize multiple zones into a single record.
Hour
The hours that you want to include in your Capacity Planning database file. You may specify a maximum of five hours or hour ranges. Leave this parameter blank to include data for all hours.
Dayname
The specification of up to five daynames to be included in the Capacity Planner database file. Leave blank to include all days. Input the first unique characters and the Capacity Planner will fill in the rest. Specification of this parameter is only valid when the input timespan is DETAIL or DAYS.
Specify common data selection SAS statements
The specification for the SYSIDs and zones or hours to be used for data selection from the CAP input file(s). Specify Y (YES) to display the SAS Statements screen that is shown in Figure 3-98. Specify R (Reset) to reset any specifications you previously made to SYSID and zone or hour.
Figure 3-98. SAS Statements Screen - Selecting Common Data
/--------------------------- SAS System Statements --------------------------\ |Command ===> Scroll ===> CSR | | | |SAS Statements for the SELECT Macro | |------------------------------------------------------------------------------| |************************************ TOP OF DATA *****************************| |==MSG> ENTER THE SAS STATEMENTS TO SET CAPAPU VALUES. | |=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 ***************************| | | --------------------------------------------------------------------------------
Using the SAS Statements screen that is shown above, you can specify your own data selection logic to apply to each CAP file that provides input data to your Capacity Planning database file. The special data element, CAPIFILE, is available to the SELECT MACRO and can be used in subsetting the input file.
The %MACRO SELECT and %MEND SELECT statements are provided for you and that they are field-protected from modification.
Insert Capacity File and Data Element Selection
If you select Option 2, Insert CAP File and Data Element Selection, on the Meta File menu, the CAP File and Data Element Selection screen that is shown in Figure 3-99 is displayed.
Figure 3-99. CAP File and Data Element Selection Screen
/------------- Capacity Planner File and Data Element Selection -------------\ |Command ===> Scroll ===> CSR | |Enter a ? in any data entry field for more information on valid values. | |Composing CAP DB File def.: SYS - System Activity Tracking File | | | |CAP file ===> WK1 (fff) - Workload Standard Application | | -------Line Commands--------| |Include CAPAPUs ===> N (Y/N) | I Insert C Copy D Delete || |Specify file exits ===> N (Y/N) | R Repeat E Calculations || | | S Depend Clauses & Label || | ----------------------------| | Sum Data | |Cmd Name Label (long name) D Type Type Order Len Output Format| | - -------- ----------------------------- - ---- ---- ----- --- -------------| | _ DATE Interval End Date | | _ RET D _____ 7 DATE7. | | _ MONTH Month of Year | | _ RET N _____ 2 _____________| | _ SYSID System Identifier | | _ RET A _____ 4 _____________| | _ YEAR Year of Century | | _ RET N _____ 2 _____________| | _ ZONE Time Zone | | _ RET A _____ 1 _____________| |******************************* BOTTOM OF DATA *******************************| | | --------------------------------------------------------------------------------
The parameters for the CAP File and Data Element Selection screen are defined as follow:
CAP file
The Capacity Planner file that contains the data elements that you want to include in your meta file or that you want to use in deriving data elements. If you are uncertain of the file name, type a question mark (?) in this field to obtain a complete selection list for your site.
Include CAPAPUs
The specification for whether the application unit (CAPAPU) data element is to be included in the summarization sequence for this file. This parameter defaults to Y (YES) if CAPAPU is defined for this meta file. The CAPAPU derivation exit is invoked for each input file observation. If you do not want to include CAPAPU in the summarization sequence, type an N (NO) in this field.
Specify file exits
The specification for CAP file processing exits. Specify a Y (YES) if you intend to code CAP file-unique data selection, or data derivation logic. If you specify a Y, the CAP File Processing Exits Menu shown in Figure 3-100 is displayed.
The display portion of this screen contains a scrollable list of the data elements that you can either include in your Capacity Planning database file or use to derive other data elements. It contains the following fields:
Cmd
The line commands are:
I (insert)
to insert a new data element.
R (repeat)
to repeat a data element.
S (depend clauses and label)
to specify independent data elements upon which this data element depends. See Figure 3-14.
C (copy)
to copy a data element.
E (expression)
to create SAS code to calculate the value of this specific data element. See Figure 3-15.
D (delete)
to delete a data element.
Name
The name of the data element. This can be either the name of a data element that exists in the input CAP file or any valid SAS name, as described in the SAS manuals. If you want to define new data elements, choose variable names that are descriptive of the values they represent.
Note that when you first see this screen, it displays only the control data elements that are always present in your Capacity Planning database file. If you attempt to modify these data elements, an error will occur. Define an additional row for each data element that you want to include in your Capacity Planning database file by typing an I (INSERT) in the Cmd column of any existing row.
If you are uncertain of the correct spelling of a CAP data element or if you would like to see a complete list of the CAP data elements available in the Capacity Planner input file, type a question mark (?) in the name field to display the screen that is shown in Figure 3-101.
Data Element Label (long name)
The data element label that is displayed on the CAP File and Data Element Selection screen and on many reports. This label is supplied automatically for input data elements.
D
The data element drop flag. Typing a D in this field makes the corresponding data element available for use in calculations through the cross-file data element definition step of the Capacity Planning database file update, but drops the data element from the resulting Capacity Planning database file. Leave the field blank to keep the corresponding data element on the Capacity Planning database file.
Sum Type
The summarization type of the data element. Summarization types are RET (retain), ACCM (accumulate), MIN (minimum), MAX (maximum), and COMP (compute).
Date type
The type of data element. This is used to validate data values and usage for the data element. Valid types are Alphanumeric (A), Numeric (N), Money (M), Time (T), Hex (H), Date (D), Time-of-day (TD), and Date-Time (DT). This value is supplied automatically for
MICS data element
s.
Order
Define the execution order of the data elements you defined by entering ordinal numeric values greater than 1000.
Note:
This is required if you are going to use this Resource Element file as input to a Meta file.
The order value is automatically defined for
MICS data element
s and Capacity Planner Control elements. Data elements that require other data elements are automatically included in the Capacity Planner database file. In particular, two variables that will not show up in the output file: @@FIRST and @@LAST.
Len
The length of the data element. This value is supplied automatically for
MICS data element
s.
Output Format
The SAS format that is used to print data element values. This value is supplied automatically for
MICS data element
s.
Figure 3-100. CAP File Processing Exits Menu
/--------------- Capacity Planner File Processing Exits Menu ----------------\ |Command ===> | | | |Inquiry Step: File & Data Element Sel.: WK1 - Workload Standard Application | | | | | |Specify file unique data selection SAS stmts. ===> N (Y/N/R) | | (file level SELECT exit) | | | |Specify new data element derivation SAS stmts. ===> N (Y/N/R) | | (file transpose and summary exit) | | | |Set expression statements for data elements. ===> N (Y/N) | | (convert SAS stmts to Expression stmts) | | | | | | | | | --------------------------------------------------------------------------------
Figure 3-100 shows the CAP File Processing Exits Menu that is displayed if you specify a Y (YES) for the Specify CAP file processing exits parameter on the CAP File and Data Element Selection screen that is shown in Figure 3-99.
The following options are available:
Specify file unique data selection SAS stmts
Specify a Y (YES) to supply SAS statements in the CAPSLCT macro, used to implement a special observation selection method.
Specify new data element derivation SAS stmts
Specify a Y (YES) to supply SAS statements in the CAPSMRY macro, used to define new data elements for the meta file and to calculate values for
MICS
derived data elements.
Set expression statements for data elements
Set to Y (YES) to convert existing Meta file SAS statements to expression statements or calculations.
The CAPSMRY exit should only be used for the setting the initial value of non-Computed variables or to transpose the CAP file. The SAS Statements necessary to set the value for a Computed variable should be placed in Expression Statements.
The following illustration describes the CAPSMRY exit.
Data Element Type
Need SAS Code in CAPSMRY?
Need Expression Statement?
Maximum
Yes, to set initial value
No, handled automatically in Meta files
Minimum
Yes, to set initial value
No, handled automatically in Meta files
Accumulated
Yes, to set initial value
No, handled automatically in Meta files
Retained
Yes, to set initial value
No, handled automatically in Meta files
Computed
No
Yes, Expression statements used in Meta files when variable is created and in subsequent Meta Files.
Figure 3-101. Converting Macros to Expression Statements
/---------------- Converting Macros to Expression Statements ----------------\ |Command ===> Scroll ===> CSR | | | |Enter the variable names that are associated with the SAS statements shown | |below. | | | |Variable SAS Statements in Macro | |-------- ------------------------------------------------------------------ | |MYVAR2__ IF CPUAVB GT 10 /* IF THE AVERAGE NUMBER OF BATCH JOBS */ | |MYVAR2__ THEN MYVAR2 = 'CHECK'; /* IS GREATER THAN 10 WE SHOULD */ | |MYVAR2__ ELSE MYVAR2 = 'OK'; /* CHECK IT OUT */ | |****************************** BOTTOM OF DATA ********************************| --------------------------------------------------------------------------------
You use this screen (see Figure 3-101) to convert existing MACRO statements into Expression Statements that calculate the value of a particular variable. In the example that is shown in Figure 3-101, the variable MYVAR2 is a user-created data element that is used to warn the user of this file whenever CPUAVB is larger than 10. This variable was originally created using the CAPSMRY MACRO. By placing "MYVAR2" in the Variable Column of this screen the Capacity Planner will automatically associate these SAS Statements with MYVAR2. When you End from this display the Capacity Planner will remove the statements from the MACRO and move them into the Expression Statement table for the variable MYVAR2.
Figure 3-102. Data Element Selection Screen
/--------------------------- Data Element Selection --------------------------\ |Command ===> Scroll ===> CSR | | | |Inquiry Step: Common Data Selection | |Input File: WK1 - Workload Standard Application | | | |Line Cmds: S Select H Data Dictionary Display | | | | Select Data Elements | |Cmd Element Data Element Label (long name) | | - -------- ---------------------------------------- | | _ CAPAPU Workload Group | | _ CPUDUR Recording Interval Time | | _ CPUTOBTM Total Time Processor Busy | | _ CPUTOUTM Total Processor Up Time | | _ DATE Interval End Date | | _ DESCRIPT Workload Group Long Name | | _ HOUR Hour of Day | | _ MVSLEVEL MVS Software Level | | _ PAGPIN Non-VIO Non-Swap Page-Ins | | _ PCATRCPU Percent of CPU Attributable to Workload | | _ PCTOTCPU Percent Total CPU Time Consumed | | | --------------------------------------------------------------------------------
If you enter a question mark (?) in the Data Element Label field of the CAP File and Data Element Selection screen that is shown in Figure 3-99, the Data Element Selection screen (Figure 3-102), which is the final screen in this series, is displayed. This screen lists the data elements in the CAP file that you specified. To include data elements in the meta file, place an S (SELECT) in the Cmd column to the left of the data element you want to include in your meta file.
Insert Cross-File Data Element Definition
If you specify data selection from more than one CAP file (using Option 2 on the Meta File menu that is shown in Figure 3-96), also insert a cross-file data element definition step in your meta file definition. Select Option 3, Insert Cross-File Data Element Definition from the Meta File Menu, to define data elements that are calculated from data elements that are contained in more than one file. This screen displays all the data elements, including the control data elements, that you selected from all CAP files.
Figure 3-103. Cross-File Data Element Definition Screen
/--------------------- Cross-File Data Element Definition -------------------\ |Command ===> Scroll ===> CSR | |Enter a ? in any data entry field for more information on valid values. | |Composing CAP DB File def.: SYS - System Activity Tracking File | | | |Specify: -------Line Commands--------| | SAS exit stmts. ===> N (Y/N/R) | I Insert C Copy D Delete || | | R Repeat E Calculations || | Expression stmts. ===> N (Y/N) | S Depend Clauses & Label || | ----------------------------| | Sum Data | |Cmd Name Label (long name) D Type Type Order Len Output Format| | - -------- ----------------------------- - ---- ---- ----- --- -------------| | _ CPUAVT Workload Group | | _ RET N 000 5 _____________| | _ DATE Workload Group 2 | | _ RET D 000 7 DATE7._______| | _ JOBCPUTM Workload Group 3 | | _ RET T 000 10 TIME14.2_____| | _ MONTH Workload Group 4 | | _ RET N 000 2 _____________| | _ SYSID Workload Group 5 | | _ RET A 000 4 _____________| | _ YEAR Workload Group 6 | | _ RET N 000 2 _____________| | _ ZONE Workload Group 7 | | _ RET A 000 1 _____________| |****************************** BOTTOM OF DATA *******************************| |------------------------------------------------------------------------------|
The parameters for the Cross-File Data Element Definition screen are defined below:
Specify SAS exit stmts
The specification for assigning SAS statements to derive cross-file elements. Specify a Y (YES) if you want to define cross-file data elements. (See Figure 3-103.)
Specify Expression stmts
The specification for defining Expression statements. Specify a Y (YES) if you want to define expression statements.
Cmd
The line commands are:
I (insert)
to insert a new data element.
R (repeat)
to repeat a data element.
S (depend clauses and label)
to specify independent data elements upon which this data element depends. See Figure 3-14.
C (copy)
to copy a data element.
E (expression)
to create SAS code to calculate the value of this specific data element. See Figure 3-15.
D (delete)
to delete a data element.
Name
The name of the data element. This can be either the name of a
MICS data element
that exists in the input CAP file or any valid SAS name, as described in the SAS manuals. If you want to define new data elements, choose variable names that are descriptive of the values they represent.
Note that the screen displays the
MICS
control data elements that are always present in your meta file. If you attempt to modify these data elements, an error will occur. Define an additional row for each data element that you want to include in your meta file by typing an I (INSERT) in the Cmd column of any existing row.
Data Element Label (long name):
The data element label that is displayed on the CAP File and Data Element Selection screen and on many reports. This label is supplied automatically for
MICS data element
s.
D
The data element drop flag. Typing a D in this field makes the corresponding data element available for use in calculations through the cross-file data element definition step of the Capacity Planning database file update, but drops the data element from the resulting Capacity Planning database file. Leave the field blank to keep the corresponding data element on the Capacity Planning database file.
Sum Type
The summarization type of the data element
RET (retain), ACCM (accumulate), MIN (minimum), MAX (maximum), and COMP (compute).
Date type
The type of data element. This is used to validate data values and usage for the data element. Valid types are Alphanumeric (A), Numeric (N), Money (M), Time (T), Hex (H), Date (D), Time-of-day (TD), and Date-Time (DT). This value is supplied automatically for
MICS data element
s.
Order
Define the execution order of the data elements you defined by entering ordinal numeric values greater than 3000.
Note
This is required if you are going to use this Resource Element file as input to a Meta file.
The order value is automatically defined for
MICS data element
s and Capacity Planner Control elements. Data elements that require other data elements are automatically included in the Capacity Planner database file. In particular, two variables could appear that will not show up in the output file: @@FIRST and @@LAST.
Len
The length of the data element. This value is supplied automatically for
MICS data element
s.
Output Format
The SAS format that is used to print data element values. This value is supplied automatically for
MICS data element
s.
Figure 3-104. SAS Statements Screen - Deriving Cross-file Data Elements
/-------------------------- SAS System Statements ---------------------------\ |Command ===> Scroll ===> CSR | | | |Inquiry Step: Cross-file data element derivation | | | |SAS Statements for the CAPMERG Macro | |------------------------------------------------------------------------------| |****** ***************************** TOP OF DATA *****************************| |==MSG> ENTER THE SAS STATEMENTS TO SET VARIABLES IN THE CROSS-FILE MERGE. | |=NOTE= %MACRO CAPMERG; <=== PLEASE DO NOT PLACE LINES BEFORE THIS LINE. | |000001 | |000002 | |000003 | |000004 | |000005 | |000006 | |000007 | |000008 | |000009 | |000010 | |=NOTE= %MEND CAPMERG; <=== PLEASE DO NOT PLACE LINES AFTER THIS LINE. | |****************************** BOTTOM OF DATA *******************************| | | |------------------------------------------------------------------------------|
Using the SAS Statements screen that is shown in Figure 3-104 above, you can code any valid SAS statements that conform to the syntax described in the SAS manuals to derive new data elements.
The %MACRO CAPMERG and %MEND CAPMERG statements are provided for you and that they are field protected from modification.
Figure 3-105. Converting Macros to Expression Statements
/---------------- Converting Macros to Expression Statements ----------------\ |Command ===> Scroll ===> CSR | | | |Enter the variable names that are associated with the SAS statements shown | |below. | | | |Variable SAS Statements in Macro | |-------- ------------------------------------------------------------------ | |RATIO___ IF CPUTOBTM GT 0 | |RATIO___ THEN RATIO = PGACPUTM / CPUTOBTM; | |RATIO___ ELSE RATIO = .; | |________ | |****************************** BOTTOM OF DATA ********************************| |------------------------------------------------------------------------------|
You use this screen (see Figure 3-105) to convert existing MACRO statements into Expression Statements that calculate the value of a particular variable. In the example that is shown in Figure 3-105, the variable RATIO is a user-created data element that corresponds to the ratio of Performance Group Activity (PGA) file CPU time that is consumed and the total Busy time of the processor. By placing "RATIO" in the Variable Column of this screen the Capacity Planner will automatically associate these SAS Statements with RATIO. When you End from this display the Capacity Planner will remove the statements from the MACRO and move them into the Expression Statement table for the variable RATIO.
Specification Processing
After you specify all of the parameters that are necessary to build your meta file, END from the Meta File menu shown in Figure 3-96 to display the Meta File screen shown in Figure 3-106.
This screen lists the file definition steps that you defined. You can change specifications for any step by typing an S on the Cmd column of the step you want to change. In the same way, you can delete, insert, or repeat a step by typing D, I, or R, respectively.
Figure 3-106. Meta File Screen
/------------------------------- Meta File --------------Validation Required.-\ |Command ===> Scroll ===> CSR | | | |Composing CAP DB File def.: SYS - System Activity Tracking File | |File definition must be validated. Enter VALIDATE to validate the file def. | |Update the capacity planning data base file ===> N (Y/N) | | | |Line Cmds: S Select I Insert D Delete R Repeat | | | |Cmd Data Base File Definition Step | | - ------------------------------------------------------------------ | | _ Meta File Definition | | _ File & Data Element Sel.: VM1 - VM/XA Standard Application | | _ File & Data Element Sel.: ES1 - MVS/ESA Standard Application | | _ Cross-File Data Element Definition | |****************************** BOTTOM OF DATA ********************************| | | | | | | | | | | | | | | |-------------------------------------------------------------------------------|
Before you execute your meta file definition inquiry, first validate it to ensure that you have defined all of the necessary steps. For instance, if you specify more than one file and data element selection step, then the online facility ensures that you also specify a cross-file data element definition step to cause the data from each of the file and data element selection steps to be merged.
You may request validation of your meta file definition inquiry by typing a V (or VALIDATE) at the Command prompt of the Meta File screen and pressing ENTER. Diagnostic messages inform you that the inquiry has been validated or why it cannot be validated so you can correct the inquiry step specifications and request validation again.
If you are unable to validate your inquiry and want to defer correcting the problems until a later time, END from this screen to save your unvalidated inquiry. The Capacity Planning Database Files screen, which displays the meta file definition inquiries in your catalog, is displayed.
After you validate your meta file definition inquiry, you have an opportunity to execute the inquiry and update the Capacity Planning database file by typing a Y at the Update Capacity Planning database file prompt and pressing ENTER. The Update Capacity Planning File screen that is shown in Figure 3-101 is displayed. After execution processing is completed, the Meta File screen is redisplayed. After you are satisfied with all the specifications, type END at the Command prompt to save your meta file definition. The Capacity Planning database File screen is then redisplayed.