3. CAPACITY PLANNING DATABASE › 3.3 Resource Element Files › 3.3.3 Resource Element File Case Studies › 3.3.3.2 Performance Group/Period Workload Tracking › 3.3.3.2.2 Control Parameters
3.3.3.2.2 Control Parameters
Figures 3-40 through 3-55 show the control screens that we
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.: PRF - Performance Group 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-40. Specifying Parameters for the Resource Element File
The specifications on the Resource Element File Definition
screen shown in Figure 3-40 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.: PRF - Performance Group 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-41. Specifying Common Data Selection
Option 1, Insert Common Data Selection, is chosen on the
Resource Element File screen shown in Figure 3-41.
/--------------------------- Common Data Selection ---------------------------\
|Command ===> |
|Enter a ? in any data entry field for more information on valid values. |
|Composing CAP DB File def.: PRF - Performance Group Example |
| |
| |
|SYSID ===> TSO1 ____ ____ ____ ____ ____ ____ ____ ____ ____ |
| ____ ____ ____ ____ ____ |
| |
|Zone ===> 1 _ _ _ _ _ _ _ _ (1 - 9) |
| |
|Hour ===> 08 - 09 14 - 15 __ - __ __ - __ __ - __ (0 - 23) |
| |
|Dayname ===> _________ _________ _________ _________ _________ |
| |
| |
| |
| |
| |
| |
| |
| |
|Specify common data selection SAS statements ===> N (Y/N/R) |
\------------------------------------------------------------------------------/
Figure 3-42. Common Data Selection Screen
The Common Data Selection screen shown in Figure 3-42
specifies that observations with SYSIDs that are equal to
TSO1, ZONE 1, and HOURs 8 and 14 are to be included in the
resource element file.
/--------------------------- Resource Element File ---------------------------\
|Option ===> 2 |
| |
|Composing CAP DB file def.: PRF - Performance Group 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-43. 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-43.
The CA MICS File and Data Element Selection screen shown in
Figure 3-44 specifies that the CA MICS PPA 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.: PRF - Performance Group Example |
|CA MICS file ===> PPA (fff) - MVS PERFORMANCE PERIOD ACTIVITY FILE |
|Input Time-Span ===> WEEKS (DETAIL/DAYS/WEEKS/MONTHS) |
|Data base (s) ===> P |
|Include CAPAPUs ===> N (Y/N) -------Line Commands--------|
|Summarize file by ===> PERFPER_ | 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 |
| - -------- ----------------------------- - ---- ---- ----- --- ------------- |
| _ PERFPER Perf Group Period |
| D RET N 050 5 _____________ |
| _ DATE Interval End Date |
| _ RET D 000 7 DATE7._______ |
| _ PPATTX Trans Terminated |
| _ ACCM N 050 13 _____________ |
| _ SYSID System Identifier |
| _ RET A 000 4 _____________ |
| _ WEEK Week of Year |
| _ RET N 000 2 _____________ |
| _ WKL01 Period 1 TSO |
| _ ACCM N 120 13 _____________ |
| _ WKL02 Period 2 TSO |
| _ ACCM N 120 13 _____________ |
|******************************* BOTTOM OF DATA *******************************|
| |
\------------------------------------------------------------------------------/
Figure 3-44. 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.: PRF - Performance Group Example |
|CA MICS file ===> PPA (fff) - MVS PERFORMANCE PERIOD ACTIVITY FILE |
|Input Time-Span ===> WEEKS (DETAIL/DAYS/WEEKS/MONTHS) |
|Data base (s) ===> P |
|Include CAPAPUs ===> N (Y/N) -------Line Commands--------|
|Summarize file by ===> PERFPER_ | 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 |
| - -------- ----------------------------- - ---- ---- ----- --- ------------- |
| _ WKL03 Period 3 TSO |
| _ ACCM N 120 13 ____________ |
| _ WKL04 Period 4 TSO |
| _ ACCM N 120 13 ____________ |
| _ WKL05 Period 5 TSO |
| _ ACCM N 120 13 ____________ |
| _ YEAR Year of Century |
| _ RET N 000 2 ____________ |
| _ ZONE Time Zone |
| _ RET A 000 1 ____________ |
|******************************* BOTTOM OF DATA *******************************|
\------------------------------------------------------------------------------/
Figure 3-44. CA MICS File and Data Element Selection Screen - Screen 2
/---------------------- CA MICS File Processing Exits Menu -------------------\
|Command ===> |
| |
|Inquiry Step: File & Data Element Sel.: PPA - MVS PERFORMANCE PERIOD ACTIVITY |
| |
| |
|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-45. CA MICS File Processing Exits Menu
The CA MICS File Processing Exits Menu shown in Figure 3-45
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.: PPA - MVS PERFORMANCE PERIOD |
| |
|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 PERFGRP = 2; |
|=NOTE= %MEND CAPSLCT; <=== PLEASE DO NOT PLACE LINES AFTER THIS LINE. |
|****** **************************** BOTTOM OF DATA ***************************|
| |
\------------------------------------------------------------------------------/
Figure 3-46. Selecting File-Unique Data
The SAS Statements screen in Figure 3-46 shows the SAS
statements that are used to subset the input data to
observations for performance group 2 only.
/-------------------------- SAS System Statements ---------------------------\
|Command ===> Scroll ===> CSR |
| |
|Inquiry Step: File & Data Element Sel.: PPA - MVS PERFORMANCE PERIOD |
| |
|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 PERFPER = 1 THEN WKL01 + PPATTX ; |
|000002 IF PERFPER = 2 THEN WKL02 + PPATTX ; |
|000003 IF PERFPER = 3 THEN WKL03 + PPATTX ; |
|000004 IF PERFPER = 4 THEN WKL04 + PPATTX ; |
|000005 IF PERFPER = 5 THEN WKL05 + PPATTX ; |
|=NOTE= %MEND CAPSMRY; <=== PLEASE DO NOT PLACE LINES AFTER THIS LINE. |
|****** **************************** BOTTOM OF DATA ***************************|
| |
\------------------------------------------------------------------------------/
Figure 3-47. Deriving New Data Elements
The SAS Statements screen in Figure 3-47 shows the SAS
statements that are used to define the new data elements.
WRK0x is the transaction count for workload x.
The CA MICS File and Data Element Selection screen shown in
Figure 3-48 specifies that the CA MICS PGA 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.: PRF - Performance Group Example |
|CA MICS file ===> PGA (fff) - MVS PERFORMANCE GROUP ACTIVITY FILE |
|Input Time-Span ===> WEEKS (DETAIL/DAYS/WEEKS/MONTHS) |
|Data base (s) ===> P |
|Include CAPAPUs ===> N (Y/N) -------Line Commands--------|
|Summarize file by ===> PERFGRP_ | 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 |
| - -------- ----------------------------- - ---- ---- ----- --- ------------- |
| _ PERFGRP Perf Group Number |
| D RET N 050 5 _____________ |
| _ DATE Interval End Date |
| _ RET D 000 7 DATE7._______ |
| _ PPATTX Trans Terminated |
| D ACCM N 050 13 ____________ |
| _ SYSID System Identifier |
| _ RET A 000 4 _____________ |
| _ WEEK Week of Year |
| _ RET N 000 2 _____________ |
| _ WKL06 Development TSO |
| _ ACCM N 120 7 _____________ |
| _ WKL07 JES |
| _ ACCM N 120 7 _____________ |
|******************************* BOTTOM OF DATA *******************************|
| |
\------------------------------------------------------------------------------/
Figure 3-48. 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.: PRF - Performance Group Example |
|CA MICS file ===> PGA (fff) - MVS PERFORMANCE GROUP ACTIVITY FILE |
|Input Time-Span ===> WEEKS (DETAIL/DAYS/WEEKS/MONTHS) |
|Data base (s) ===> P |
|Include CAPAPUs ===> N (Y/N) -------Line Commands--------|
|Summarize file by ===> PERFGRP_ | 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 |
| - -------- ----------------------------- - ---- ---- ----- --- ------------- |
| _ WKL08 Overhead |
| _ ACCM N 120 7 _____________ |
| _ YEAR Year of Century |
| _ RET N 000 2 _____________ |
| _ ZONE Time Zone |
| _ RET A 000 1 _____________ |
|******************************* BOTTOM OF DATA *******************************|
\------------------------------------------------------------------------------/
Figure 3-48. CA MICS File and Data Element Selection Screen - Screen 2
/---------------------- CA MICS File Processing Exits Menu -------------------\
|Command ===> |
| |
|Inquiry Step: File & Data Element Sel.: PGA - MVS PERFORMANCE GROUP ACTIVITY |
| |
| |
|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-49. CA MICS File Processing Exits Menu
The CA MICS File Processing Exits Menu shown in Figure 3-49
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.: PPA - MVS PERFORMANCE PERIOD |
| |
|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 PERFGRP EQ 7 THEN WKL06 + PGATTX ; |
|000002 ELSE IF PERFGRP EQ 62 THEN WKL07 + PGATTX ; |
|000003 ELSE IF PERFGRP NE 2 THEN WKL08 + PGATTX ; |
|=NOTE= %MEND CAPSMRY; <=== PLEASE DO NOT PLACE LINES AFTER THIS LINE. |
|****** **************************** BOTTOM OF DATA ***************************|
| |
\------------------------------------------------------------------------------/
Figure 3-50. Deriving New Data Elements
The SAS Statements screen in Figure 3-50 shows the SAS
statements that are used to define the new data elements.
WRK0x is the transaction count for workload x.
/--------------------------- Resource Element File ---------------------------\
|Option ===> 3 |
| |
|Composing CAP DB file def.: PRF - Performance Group 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-51. Specifying a Cross-File Data Element Definition
Option 3, Insert Cross-File Data Element Definition, is
chosen on the Resource Element File screen shown in Figure
3-51.
/-------------------------- SAS System Statements ---------------------------\
|Command ===> Scroll ===> CSR |
| |
|Inquiry Step: File & Data Element Sel.: PPA - MVS PERFORMANCE PERIOD |
| |
|SAS Statements for the CAPMERG Macro |
|------------------------------------------------------------------------------|
|****** ***************************** TOP OF DATA *****************************|
|==MSG> SPECIFY SAS STATEMENTS TO SET VARIABLES IN THE CROSS-FILE MERGE. |
|=NOTE= %MACRO CAPMERG; <=== PLEASE DO NOT PLACE LINES BEFORE THIS LINE. |
|000001 WKL01 = WKL01 / 10 ; |
|000002 WKL02 = WKL02 / 10 ; |
|000003 WKL03 = WKL03 / 10 ; |
|000004 WKL04 = WKL04 / 10 ; |
|000005 WKL05 = WKL05 / 10 ; |
|000006 WKL06 = WKL06 / 10 ; |
|000007 WKL07 = WKL07 / 10 ; |
|000008 WKL08 = WKL08 / 10 ; |
|=NOTE= %MEND CAPMERG; <=== PLEASE DO NOT PLACE LINES AFTER THIS LINE. |
|****** **************************** BOTTOM OF DATA ***************************|
| |
\------------------------------------------------------------------------------/
Figure 3-52. Deriving Cross-File Data Elements
The SAS Statements screen shown in Figure 3-52 specifies the
SAS statements for performing calculations on data elements
from more than one CA MICS input file.
/--------------------------- Resource Element File --------Inquiry Validated.-\
|Command ===> Scroll ===> CSR |
| |
|Composing CAP DB File def.: PRF - Performance Group 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.: PPA - MVS PERFORMANCE PERIOD ACTIVITY FILE |
| _ File & Data Element Sel.: PGA - MVS PERFORMANCE GROUP ACTIVITY FILE |
| _ Cross-File Data Element Definition |
|****************************** BOTTOM OF DATA ********************************|
| |
| |
| |
| |
| |
| |
\------------------------------------------------------------------------------/
Figure 3-53. Executing the Inquiry
After the resource element file definition parameters are
specified, the Resource Element File screen is used to
validate the inquiry. Figure 3-53 shows this screen after
VALIDATE is typed at the Command prompt.
/----------------------- Update Capacity Planning File ------- Confirm Save.-\
|Command ===> |
| |
|Modifying CAP DB File def.: PRF - Performance Group 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-54. Saving the Inquiry
The Update Capacity Planning File shown in Figure 3-54 is
used to save the inquiry so that it can be executed.
/----------------------- Update Capacity Planning File -------------------------\
|Command ===> |
| |
|Composing CAP DB File def.: PRF - Performance Group 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 - 09 (0 - 99) |
|Archive generation number ===> ___ (0 to -99) |
| |
|Starting date of update ===> _______ (ddmonyy) |
|Number of months to select ===> 9___ (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-55. Executing the Inquiry
Cycles 1 through 9 are specified as input to the database
loading process on the Update Capacity Planning File screen
shown in Figure 3-55. The updated resource element file will
be printed after the update is complete.
Copyright © 2014 CA.
All rights reserved.
|
|