3. CAPACITY PLANNING DATABASE › 3.3 Resource Element Files › 3.3.3 Resource Element File Case Studies › 3.3.3.1 Extended Example I/O Workload Analysis › 3.3.3.1.2 Control Parameters
3.3.3.1.2 Control Parameters
Figures 3-27 through 3-38 show the control screens that were
used to create and execute this resource element file
definition example.
/---------------------- 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) |
\------------------------------------------------------------------------------/
Figure 3-27. Specifying Parameters for the Resource Element File
The specifications on the Resource Element File Definition
screen shown in Figure 3-27 do the following:
o Set the timespan to MONTHS
o Set the summary level to ZONE
/--------------------------- Resource Element File ---------------------------\
|Option ===> 1 |
| |
|Composing CAP DB file def.: CHN - I/O Channel Example |
| |
| |
| 1 - Insert Common Data Selection |
| Specify data selection criteria to apply to ALL files. |
| 2 - Insert CA MICS File and Data Element Selection |
| Select a CA MICS file and data elements. |
| 3 - Insert Cross-File Data Element Definition |
| Specify cross-file data element derivations. |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
\------------------------------------------------------------------------------/
Figure 3-28. Specifying Common Data Selection
Option 1, Insert Common Data Selection, is chosen on the
Resource Element File screen shown in Figure 3-27.
/--------------------------- Common Data Selection ---------------------------\
|Command ===> |
|Enter a ? in any data entry field for more information on valid values. |
|Composing CAP DB File def.: CHN - I/O Channel Example |
| |
| |
|SYSID ===> TSO1 TSO2 ____ ____ ____ ____ ____ ____ ____ ____ |
| ____ ____ ____ ____ ____ |
| |
|Zone ===> 1 2 _ _ _ _ _ _ _ (1 - 9) |
| |
|Hour ===> __ - __ __ - __ __ - __ __ - __ __ - __ (0 - 23) |
| |
|Dayname ===> _________ _________ _________ _________ _________ |
| |
| |
| |
| |
| |
| |
| |
| |
|Specify common data selection SAS statements ===> N (Y/N/R) |
\------------------------------------------------------------------------------/
Figure 3-29. Common Data Selection Screen
The Common Data Selection screen shown in Figure 3-29
specifies that observations with SYSIDs that are equal to
TSO1 or TSO2, and with ZONEs 1 or 2 are to be included in the
resource element data file. No user-defined common data
selection statements are to be specified.
/--------------------------- Resource Element File ---------------------------\
|Option ===> 2 |
| |
|Composing CAP DB file def.: CHN - I/O Channel Example |
| |
| |
| 1 - Insert Common Data Selection |
| Specify data selection criteria to apply to ALL files. |
| 2 - Insert CA MICS File and Data Element Selection |
| Select a CA MICS file and data elements. |
| 3 - Insert Cross-File Data Element Definition |
| Specify cross-file data element derivations. |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
\------------------------------------------------------------------------------/
Figure 3-30. Selecting CA MICS Files and Data Elements
Option 2, Insert CA MICS File and Data Selection, is chosen
on the Resource Element File screen shown in Figure 3-30.
The CA MICS File and Data Element Selection screen shown in
Figures 3-31 and 3-32 specifies that the CA MICS PCA file in
database unit P is to be used. The data elements to be
included in the resource element file are listed. A Y
specified for the Specify CA MICS file processing exits
parameter indicates that user-defined logic for selecting
specific channels is to be used.
/-------------------- CA MICS 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.: CHN - I/O Channel Example |
|CA MICS file ===> PCA (fff) - PHYSICAL CHANNEL ACTIVITY FILE |
|Input Time-Span ===> MONTHS (DETAIL/DAYS/WEEKS/MONTHS) |
|Data base (s) ===> P |
|Include CAPAPUs ===> N (Y/N) -------Line Commands--------|
|Summarize file by ===> CHANNEL_ | 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 |
| - -------- ----------------------------- - ---- ---- ----- --- ------------- |
| _ CHANNEL Physical Channel |
| D RET A 050 2 _____________ |
| _ CHAN1BS Channel 1 Busy |
| _ COMP N 050 7 PERCENT______ |
| _ CHAN1CNT Channel 1 Start |
| _ ACCM N 050 7 _____________ |
| _ CHAN2BS Channel 2 Busy |
| _ COMP N 050 7 PERCENT______ |
| _ CHAN2CNT Channel 2 Start |
| _ ACCM N 050 7 _____________ |
| _ CHAN3BS Channel 3 Busy |
| _ COMP N 050 7 PERCENT______ |
| _ CHAN3CNT Channel 3 Start |
| _ ACCM N 050 7 _____________ |
|******************************* BOTTOM OF DATA *******************************|
| |
\------------------------------------------------------------------------------/
Figure 3-31. CA MICS File and Data Element Selection Screen - Screen 1
/-------------------- CA MICS File and Data Element Selection ---------------\
|Command ===> Scroll ===> CSR |
|Enter a ? in any data entry field for more information on valid values. |
|Modifying CAP DB File def.: CHN - I/O Channel Example |
|CA MICS file ===> PCA (fff) - PHYSICAL CHANNEL ACTIVITY FILE |
|Input Time-Span ===> MONTHS (DETAIL/DAYS/WEEKS/MONTHS) |
|Data base (s) ===> P |
|Include CAPAPUs ===> N (Y/N) -------Line Commands--------|
|Summarize file by ===> CHANNEL_ | 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 |
| - -------- ----------------------------- - ---- ---- ----- --- ------------- |
| _ CHAN4BS Channel 4 Busy |
| _ COMP N 050 7 PERCENT |
| _ CHAN4CNT Channel 4 Start |
| _ ACCM N 050 7 _____________ |
| _ CHAN5BS Channel 5 Busy |
| _ COMP N 050 7 PERCENT______ |
| _ CHAN5CNT Channel 5 Start |
| _ ACCM N 050 7 _____________ |
| _ DATE Interval End Date |
| _ RET D 000 7 DATE7._______ |
| _ MONTH Month of Year |
| _ RET N 000 2 _____________ |
| _ PCAPCBSY |
| D COMP N 050 5 PERCENT______ |
|******************************* BOTTOM OF DATA *******************************|
| |
\------------------------------------------------------------------------------/
Figure 3-31. CA MICS File and Data Element Selection Screen - Screen 2
/-------------------- CA MICS File and Data Element Selection ---------------\
|Command ===> Scroll ===> CSR |
|Enter a ? in any data entry field for more information on valid values. |
|Modifying CAP DB File def.: CHN - I/O Channel Example |
|CA MICS file ===> PCA (fff) - PHYSICAL CHANNEL ACTIVITY FILE |
|Input Time-Span ===> MONTHS (DETAIL/DAYS/WEEKS/MONTHS) |
|Data base (s) ===> P |
|Include CAPAPUs ===> N (Y/N) -------Line Commands--------|
|Summarize file by ===> CHANNEL_ | I Insert C Copy D Delete ||
|Specify file exits ===> Y (Y/N) | R Repeat E Calculations ||
| | S Depend Clauses & Label ||
| ----------------------------|
| Sum Data |
|Cmd Name Label (long name) D Type Type Order Len Output-Format |
| - -------- ----------------------------- - ---- ---- ----- --- ------------- |
| _ PCASIO Successful I/Os |
| D ACCM N 050 13 _____________ |
| _ SYSID System Identifier |
| _ RET A 000 4 _____________ |
| _ YEAR Year of Cent |
| _ RET N 000 2 _____________ |
| _ ZONE Time Zone |
| _ RET A 000 1 _____________ |
|******************************* BOTTOM OF DATA *******************************|
| |
\------------------------------------------------------------------------------/
Figure 3-32. CA MICS File and Data Element Selection Screen - Screen 3
/---------------------- CA MICS File Processing Exits Menu -------------------\
|Command ===> |
| |
|Inquiry Step: File & Data Element Sel.: PCA - PHYSICAL CHANNEL ACTIVITY FILE |
| |
| |
|Specify file unique data selection SAS stmts. ===> Y (Y/N/R) |
| (file level SELECT exit) |
| |
|Specify new data element derivation SAS stmts. ===> Y (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-33. CA MICS File Processing Exits Menu
The CA MICS File Processing Exits Menu shown in Figure 3-33
indicates that both data selection and data element
derivation logic are to be defined by the user.
/--------------------------- SAS System Statements --------------------------\
|Command ===> Scroll ===> CSR |
| |
|Inquiry Step: File & Data Element Sel.: PCA - PHYSICAL CHANNEL ACTIVITY FILE|
| |
|SAS Statements for the CAPSLCT Macro |
|------------------------------------------------------------------------------|
|****** ***************************** TOP OF DATA *****************************|
|==MSG> SPECIFY SAS STATEMENTS TO SUBSET THIS PARTICULAR FILE. |
|=NOTE= %MACRO CAPSLCT; <=== PLEASE DO NOT PLACE LINES BEFORE THIS LINE. |
|000001 IF CHANNEL = '1' OR CHANNEL = '2' OR CHANNEL = '3' OR |
|000002 CHANNEL = '4' OR CHANNEL = '5'; |
|=NOTE= %MEND CAPSLCT; <=== PLEASE DO NOT PLACE LINES AFTER THIS LINE. |
|****** **************************** BOTTOM OF DATA ***************************|
| |
\------------------------------------------------------------------------------/
Figure 3-34. Selecting File-Unique Data
The SAS Statements screen in Figure 3-34 shows the SAS
statements that are to be used to subset the input data to
observations for channels 1 through 5 only.
/-------------------------- SAS System Statements ---------------------------\
|Command ===> Scroll ===> CSR |
| |
|Inquiry Step: File & Data Element Sel.: PCS - PHYSICAL CHANNEL ACTIVITY FILE|
| |
|SAS Statements for the CAPSMRY Macro |
|------------------------------------------------------------------------------|
|****** ***************************** TOP OF DATA *****************************|
|==MSG> SPECIFY SAS STATEMENTS FOR TRANSPOSING THE FILE OR TO SET VARIABLES. |
|=NOTE= %MACRO CAPSMRY; <=== PLEASE DO NOT PLACE LINES BEFORE THIS LINE. |
|000001 IF CHANNEL = '1' THEN CHAN1BS + PCAPCBSY; |
|000002 IF CHANNEL = '1' THEN CHAN1CNT + PCASIO; |
|000003 IF CHANNEL = '2' THEN CHAN2BS + PCAPCBSY; |
|000004 IF CHANNEL = '2' THEN CHAN2CNT + PCASIO; |
|000005 IF CHANNEL = '3' THEN CHAN3BS + PCAPCBSY; |
|000006 IF CHANNEL = '3' THEN CHAN3CNT + PCASIO; |
|000007 IF CHANNEL = '4' THEN CHAN4BS + PCAPCBSY; |
|000008 IF CHANNEL = '4' THEN CHAN4CNT + PCASIO; |
|000009 IF CHANNEL = '5' THEN CHAN5BS + PCAPCBSY; |
|000010 IF CHANNEL = '5' THEN CHAN5CNT + PCASIO; |
|=NOTE= %MEND CAPSMRY; <=== PLEASE DO NOT PLACE LINES AFTER THIS LINE. |
|****** **************************** BOTTOM OF DATA ***************************|
| |
\------------------------------------------------------------------------------/
Figure 3-35. Deriving New Data Elements
The SAS Statements screen in Figure 3-35 shows the SAS
statements that are to be used to define the new data
elements. CHANxBS is the Channel Busy percentage for channel
x while CHANxCNT is the SIO count for the same channel.
/--------------------------- Resource Element File --------Inquiry Validated.-\
|Command ===> Scroll ===> CSR |
| |
|Composing CAP DB File def.: CHN - I/O Channel Example |
| |
|Update the capacity planning data base file ===> Y (Y/N) |
| |
|Line Cmds: S Select I Insert D Delete R Repeat |
| |
|Cmd Data Base File Definition Step |
| - ------------------------------------------------------------------ |
| _ Resource Element File Definition |
| _ Common Data Selection |
| _ File & Data Element Sel.: PCA - PHYSICAL CHANNEL ACTIVITY FILE |
|****************************** BOTTOM OF DATA ********************************|
| |
| |
| |
| |
| |
| |
| |
| |
\------------------------------------------------------------------------------/
Figure 3-36. Validating the Inquiry
After the resource element file definition parameters are
specified, the Resource Element File screen is used to
validate the inquiry. Figure 3-36 shows this screen after
VALIDATE is typed at the Command prompt.
/----------------------- Update Capacity Planning File -------- Confirm Save.-\
|Command ===> |
| |
|Modifying CAP DB File def.: CHN - I/O Channel Example |
| |
| |
|This file definition has been changed and must be saved before updating the |
|file. |
| |
| |
|Do you wish to save the file definition and update the file? ===> YES (YES/NO) |
| |
| |
| |
| |
|Instructions: |
| |
| Press ENTER key to save the file definition and update the file. |
| |
| Reply NO and press enter key to cancel the file update request. |
| |
| |
| |
\------------------------------------------------------------------------------/
Figure 3-37. Saving the Inquiry
The Update Capacity Planning File screen shown in Figure 3-37
is used to save the inquiry so that it can be executed.
/----------------------- Update Capacity Planning File -------------------------\
|Command ===> |
| |
|Composing CAP DB File def.: CHN - I/O Channel Example |
| |
|Type of update ===> INITIALIZE (INITIALIZE/UPDATE) |
|Replace existing file? ===> N (Y/N) |
| |
|Input data source ===> ONLINE (ARCHIVE/ONLINE) |
|CA MICS file cycle(s) ===> 01 - 12 (0 - 99) |
|Archive generation number ===> ___ (0 to -99) |
| |
|Starting date of update ===> _______ (ddmonyy) |
|Number of months to select ===> 12__ (1 to 9999) |
| |
|Mode of execution ===> BATCH (BATCH/FOREGROUND) |
| |
|List updated file contents? ===> YES (YES/NO) |
| |
| |
|Press END to invoke MICF inquiry execution to update the resource element file.|
|Enter CANCEL to terminate the resource element file update. |
| |
\------------------------------------------------------------------------------/
Figure 3-38. Executing the Inquiry
Cycles 1 through 12 are specified as input to the database
loading process on the Update Capacity Planning File screen
shown in Figure 3-38. The updated resource element file will
be printed after the update is complete.
Copyright © 2014 CA.
All rights reserved.
|
|