3. CAPACITY PLANNING DATABASE › 3.3 Resource Element Files › 3.3.3 Resource Element File Case Studies › 3.3.3.5 System Workload and Performance Profile › 3.3.3.5.2 Control Parameters
3.3.3.5.2 Control Parameters
Figures 3-80 through 3-91 show the control screens used to
create and execute this resource element file example.
/---------------------- Resource Element File Definition ---------------------\
|Command ===> |
|Enter a ? in any data entry field for more information on valid values. |
| CAP DB File def.: WKL - System Workload Example |
| |
|Summarization Level |
| Primary ===> WEEKS (DAYS/WEEKS/MONTHS) |
| Secondary ===> ZONE (ZONE/HOUR/ENDTS/DAYNAME) |
| |
|Amount of data retained ===> 60 (1-9999 weeks) |
|Age of oldest forecast ===> 24 (1-9999 weeks) |
|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 ===> N (Y/N) |
\------------------------------------------------------------------------------/
Figure 3-80. Resource Element File Definition Screen
The specifications on the Resource Element File Definition
screen shown in Figure 3-80 do the following:
o Set the timespan to WEEKS
o Set the summary level to ZONE
/--------------------------- Resource Element File ---------------------------\
|Option ===> 1 |
| |
|Composing CAP DB file def.: WKL - System Workload 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-81. Specifying Common Data
Option 1, Insert Common Data Selection, is chosen on the
Resource Element File screen shown in Figure 3-81.
/--------------------------- Common Data Selection ---------------------------\
|Command ===> |
|Enter a ? in any data entry field for more information on valid values. |
|Composing CAP DB File def.: WKL - System Workload Example |
| |
| |
|SYSID ===> TSO1 ____ ____ ____ ____ ____ ____ ____ ____ ____ |
| ____ ____ ____ ____ ____ |
| |
|Zone ===> 1 _ _ _ _ _ _ _ _ (1 - 9) |
| |
|Hour ===> __ - __ __ - __ __ - __ __ - __ __ - __ (0 - 23) |
| |
|Dayname ===> _________ _________ _________ _________ _________ |
| |
| |
| |
| |
| |
| |
| |
| |
|Specify common data selection SAS statements ===> N (Y/N/R) |
\------------------------------------------------------------------------------/
Figure 3-82. Common Data Selection Screen
The Common Data Selection screen shown in Figure 3-82
specifies that observations with SYSIDs equal to TSO1 and
with ZONE 1 are to be included in the resource element data
file.
/--------------------------- Resource Element File ---------------------------\
|Option ===> 2 |
| |
|Composing CAP DB file def.: WKL - System Workload 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-83. Specifying CA MICS Files and Data Elements
Option 2, Insert CA MICS File and Data Element Selection, is
chosen on the Resource Element File screen shown in Figure
3-83.
The CA MICS File and Data Element Selection screen shown in
Figure 3-84 specifies that the CA MICS CPU file in database
unit P is to be used. The data elements to be included in
the resource element file or to be used to derive non-CA MICS
data elements are listed.
/-------------------- 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.: WKL - System Workload Example |
|CA MICS file ===> CPU (fff) - CPU PROCESSOR ACTIVITY FILE |
|Input Time-Span ===> WEEKS (DETAIL/DAYS/WEEKS/MONTHS) |
|Data base (s) ===> P |
|Include CAPAPUs ===> N (Y/N) -------Line Commands--------|
|Summarize file by ===> ________ | 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 |
| - -------- ----------------------------- - ---- ---- ----- --- ------------- |
| _ CPUMPBS Avg Pct Busy 0-1 |
| _ COMP N 120 7 MAPCT._______ |
| _ CPUMXT Max TSO Users |
| _ MAX N 050 7 _____________ |
| _ CPUPCOBS Pct Busy CPU 0 |
| D COMP N 050 7 MAPCT._______ |
| _ CPUPC1BS Pct Busy CPU 1 |
| D COMP N 050 7 MAPCT._______ |
| _ DATE Interval End Date |
| _ RET D 000 7 DATE7._______ |
| _ MONTH Month of Year |
| _ RET N 000 2 _____________ |
| _ SYSID System Identifier |
| _ RET A 000 4 _____________ |
|******************************* BOTTOM OF DATA *******************************|
| |
\------------------------------------------------------------------------------/
Figure 3-84. 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.: WKL - System Workload Example |
|CA MICS file ===> CPU (fff) - CPU PROCESSOR ACTIVITY FILE |
|Input Time-Span ===> WEEKS (DETAIL/DAYS/WEEKS/MONTHS) |
|Data base (s) ===> P |
|Include CAPAPUs ===> N (Y/N) -------Line Commands--------|
|Summarize file by ===> ________ | 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 |
| - -------- ----------------------------- - ---- ---- ----- --- ------------- |
| _ YEAR Year of Century |
| _ RET N 000 2 _____________ |
| _ ZONE Time Zone |
| _ RET A 000 1 _____________ |
\------------------------------------------------------------------------------/
Figure 3-84. CA MICS File and Data Element Selection Screen - Screen 2
/---------------------- CA MICS File Processing Exits Menu -------------------\
|Command ===> |
| |
|Inquiry Step: File & Data Element Sel.: CPU - CPU PROCESSOR ACTIVITY FILE |
| |
| |
|Specify file unique data selection SAS stmts. ===> N (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-85. CA MICS File Processing Exits Menu
The CA MICS File Processing Exits Menu shown in Figure 3-85
indicates that the data element derivation logic is to be
defined by the user.
/-------------------------- SAS System Statements ---------------------------\
|Command ===> Scroll ===> CSR |
| |
|Inquiry Step: File & Data Element Sel.: CPU - CPU PROCESSOR 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 CPUMPBS = (CPUPCOBS + CPUPC1BS) /2 ; |
|=NOTE= %MEND CAPSMRY; <=== PLEASE DO NOT PLACE LINES AFTER THIS LINE. |
|****** **************************** BOTTOM OF DATA ***************************|
| |
\------------------------------------------------------------------------------/
Figure 3-86. Creating a User-defined Data Element
The SAS Statements screen in Figure 3-86 shows the SAS
statement used to compute the user-defined data element,
CPUMBPS.
/-------------------- 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.: WKL - System Workload Example |
|CA MICS file ===> PAG (fff) - MVS PAGING ACTIVITY FILE |
|Input Time-Span ===> WEEKS (DETAIL/DAYS/WEEKS/MONTHS) |
|Data base (s) ===> P |
|Include CAPAPUs ===> N (Y/N) -------Line Commands--------|
|Summarize file by ===> ________ | 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 000 7 DATE7._______ |
| _ MONTH Month of Year |
| _ RET N 000 2 _____________ |
| _ PAGPSSPG Sys Paging/Second |
| _ COMP N 050 7 _____________ |
| _ SYSID System Identifier |
| _ RET A 000 4 _____________ |
| _ YEAR Year of Century |
| _ RET N 000 2 _____________ |
| _ ZONE Time Zone |
| _ RET A 000 1 _____________ |
\------------------------------------------------------------------------------/
Figure 3-87. CA MICS File and Data Element Selection Screen
The CA MICS File and Data Element Selection screen shown in
Figure 3-87 specifies that the CA MICS PAG File in database
unit P is to be used. The data elements to be included in
the resource element file are listed.
The CA MICS File and Data Element Selection screen shown in
Figure 3-88 specifies that the CA MICS TSO file in database
unit P is to be used. The data elements to be included in
the resource element file are listed.
/-------------------- 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.: WKL - System Workload Example |
|CA MICS file ===> TSO (fff) - TSO SYSTEM ACTIVITY FILE |
|Input Time-Span ===> WEEKS (DETAIL/DAYS/WEEKS/MONTHS) |
|Data base (s) ===> P |
|Include CAPAPUs ===> N (Y/N) -------Line Commands--------|
|Summarize file by ===> ________ | 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 000 7 DATE7._______ |
| _ MONTH Month of Year |
| _ RET N 000 2 _____________ |
| _ SYSID System Identifier |
| _ RET A 000 4 _____________ |
| _ TSOAVSTM Avg Short Response |
| _ COMP N 050 7 TIME.________ |
| _ TSOAVTTM Avg Response All |
| _ COMP N 050 7 TIME.________ |
| _ TSONOLOG User Logons |
| _ ACCM N 050 7 _____________ |
| _ TSOUPTM TSO Avail Time |
| _ ACCM N 050 7 TIME.________ |
\------------------------------------------------------------------------------/
Figure 3-88. 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.: WKL - System Workload Example |
|CA MICS file ===> TSO (fff) - TSO SYSTEM ACTIVITY FILE |
|Input Time-Span ===> WEEKS (DETAIL/DAYS/WEEKS/MONTHS) |
|Data base (s) ===> P |
|Include CAPAPUs ===> N (Y/N) -------Line Commands--------|
|Summarize file by ===> ________ | 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 |
| - -------- ----------------------------- - ---- ---- ----- --- ------------- |
| _ YEAR Year of Century |
| _ RET N 000 2 _____________ |
| _ ZONE Time Zone |
| _ RET A 000 1 _____________ |
\------------------------------------------------------------------------------/
Figure 3-88. CA MICS File and Data Element Selection Screen - Screen 2
/--------------------------- Resource Element File --------Inquiry Validated.-\
|Command ===> Scroll ===> CSR |
| |
|Composing CAP DB File def.: WKL - System Workload 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.: CPU - CPU PROCESSOR ACTIVITY FILE |
| _ File & Data Element Sel.: PAG - MVS PAGING ACTIVITY FILE |
| _ File & Data Element Sel.: TSO - TSO SYSTEM ACTIVITY FILE |
| _ Cross-File Data Element Definition |
|****************************** BOTTOM OF DATA ********************************|
| |
| |
| |
| |
| |
\------------------------------------------------------------------------------/
Figure 3-89. 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-89 shows this screen after
VALIDATE is typed at the Command prompt.
/----------------------- Update Capacity Planning File -------- Confirm Save.-\
|Command ===> |
| |
|Modifying CAP DB File def.: WKL - System Workload 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-90. Saving the Inquiry
The Update Capacity Planning File screen shown in Figure 3-90
is used to save the inquiry so that it can be executed.
/----------------------- Update Capacity Planning File -------------------------\
|Command ===> |
| |
|Composing CAP DB File def.: WKL - System Workload 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 - 26 (0 - 99) |
|Archive generation number ===> ___ (0 to -99) |
| |
|Starting date of update ===> _______ (ddmonyy) |
|Number of months to select ===> 26__ (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-91. Executing the Inquiry
Cycles 1 through 26 are specified as input to the database
loading process on the Update Capacity Planning File screen
shown in Figure 3-91. The updated resource element file
will be printed after the update is complete.
Copyright © 2014 CA.
All rights reserved.
|
|