Performance Group/Period Workload Tracking (Resource Element Files)
In this performance group/period workload tracking example, an analytic model was developed using the
MICS
MVS Model Generator to represent the peak morning and afternoon hours workload (that is, 8 AM to 9AM and 2PM to 3PM) of a 3083 CPU, SYSID TSO1.micsrm140cd
In this performance group/period workload tracking example, an analytic model was developed using the
MICS
MVS Model Generator to represent the peak morning and afternoon hours workload (that is, 8 AM to 9AM and 2PM to 3PM) of a 3083 CPU, SYSID TSO1.Problem Description
The following chart represents the workloads that were defined to the model:
WORKLOAD | PERFORMANCE GROUPS AND/OR PERIODS |
1 - Period 1 TSO | Performance Group 2 Period 1 |
2 - Period 2 TSO | Performance Group 2 Period 2 |
3 - Period 3 TSO | Performance Group 2 Period 3 |
4 - Period 4 TSO | Performance Group 2 Period 4 |
5 - Period 5 TSO | Performance Group 2 Period 5 |
6 - Development TSO | Performance Group 7 |
7 - JES | Performance Group 62 |
8 - Overhead | All Other Performance Groups |
Although the analytic model was validated for the selected period, there are still two other questions that must be answered:
- Is the selected day representative of the same time periods on other days?
- How can the workload transaction arrival rates be expected to grow in the future?
A resource element file was used to collect 12 weeks of data from ZONE 1 (Monday through Friday prime shift) for the workload. You can compare these values to the transaction counts reported for the modeled interval to see if the modeled interval is similar to the historical data. (Later in this document, we show how you can use the workload forecasting program to estimate the future values of the workload transaction arrival rates.) These values are assigned by testing the value of the CHANNEL data element and then assigning the PCASIO and PCAPCBSY values to the user-defined data elements. After the data step in which the user summary exit is invoked, the observations are sorted into the default summary sequence for the final merge step. This summary sequence is SYSID ZONE YEAR timespan The records are then merged with the default sequence key. After the records are merged, the program drops the summary and drop variables, resulting in a single record that is produced for each month that contains the five channel utilizations (CHAN1BS through CHAN5BS) and the five SIO counts (CHAN1CNT through CHAN5CNT).
Control Parameters
Figures 3-40 through 3-55 show the control screens that we used to create and execute this resource element file example.
Figure 3-40. Specifying Parameters for the Resource Element File
/---------------------- 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) | --------------------------------------------------------------------------------
The specifications on the Resource Element File Definition screen that is shown in Figure 3-40 do the following:
- Set the timespan to WEEKS
- Set the summary level to ZONE
Figure 3-41. Specifying Common Data Selection
/--------------------------- 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. | | | | | | | | | | | | | | | | | | | | | | | --------------------------------------------------------------------------------
Option 1, Insert Common Data Selection, is chosen on the Resource Element File screen that is shown in Figure 3-41.
Figure 3-42. 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.: 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) | --------------------------------------------------------------------------------
The Common Data Selection screen that is 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.
Figure 3-43. Selecting
MICS
Files and Data Elements/--------------------------- 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. | | | | | | | | | | | | | | | | | | | | | | | --------------------------------------------------------------------------------
Option 2, Insert
MICS
File and Data Selection, is chosen on the Resource Element File screen that is shown in Figure 3-43.The
MICS
File and Data Element Selection screen that is shown in Figure 3-44 specifies that the 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-MICS data element
s are listed.Figure 3-44.
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. | |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.
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.: 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-45.
MICS
File Processing Exits Menu/---------------------- 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.) | | | | | | | | | | | | | | | | | | | | | --------------------------------------------------------------------------------
The
MICS
File Processing Exits Menu that is shown in Figure 3-45 indicates that both data selection and data element derivation logic are to be defined by the user.Figure 3-46. Selecting File-Unique Data
/-------------------------- 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 ***************************| | | --------------------------------------------------------------------------------
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.
Figure 3-47. Deriving New Data Elements
/-------------------------- 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 ***************************| | | --------------------------------------------------------------------------------
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
MICS
File and Data Element Selection screen that is shown in Figure 3-48 specifies that the 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-MICS data element
s are listed.Figure 3-48.
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. | |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.
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.: 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-49.
MICS
File Processing Exits Menu/---------------------- 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.) | | | | | | | | | | | | | | | | | | | --------------------------------------------------------------------------------
The
MICS
File Processing Exits Menu that is shown in Figure 3-49 indicates that the data element derivation logic is to be defined by the user.Figure 3-50. Deriving New Data Elements
/--------------------------- 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 ***************************| | | --------------------------------------------------------------------------------
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.
Figure 3-51. Specifying a Cross-File Data Element Definition
/--------------------------- 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. | | | | | | | | | | | | | | | | | | | | | | | --------------------------------------------------------------------------------
Option 3, Insert Cross-File Data Element Definition, is chosen on the Resource Element File screen that is shown in Figure 3-51.
Figure 3-52. Deriving Cross-File Data Elements
/-------------------------- 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 ***************************| | | --------------------------------------------------------------------------------
The SAS Statements screen that is shown in Figure 3-52 specifies the SAS statements for performing calculations on data elements from more than one
MICS
input file.Figure 3-53. Executing the Inquiry
/--------------------------- 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 ********************************| | | | | | | | | | | | | --------------------------------------------------------------------------------
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.
Figure 3-54. Saving the Inquiry
/----------------------- 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. | | | | | | | --------------------------------------------------------------------------------
The Update Capacity Planning File that is shown in Figure 3-54 is used to save the inquiry so that it can be executed.
Figure 3-55. Executing the Inquiry
/----------------------- 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. | | | --------------------------------------------------------------------------------
Cycles 1 through 9 are specified as input to the database loading process on the Update Capacity Planning File screen that is shown in Figure 3-55. The updated resource element file will be printed after the update is complete.
Output Report
The following figure shows the output that is created by the PROC PRINT of the updated data set.
Figure 3-56 Resource Element File Contents Report
CA MICS Capacity Planner OBS DATE SYSID WEEK YEAR ZONE WKL06 WKL07 WKL08 WKL01 WKL02 WKL03 WKL04 WKL05 1 25JUL98 TSO1 30 98 1 2565.9 0.0 1301.3 11102.5 1270.9 45.0 0.4 1.4 2 31JUL98 TSO1 31 98 1 2155.1 0.0 1352.6 11026.7 1251.8 49.3 0.6 0.8 3 07AUG98 TSO1 32 98 1 2148.7 0.0 1387.4 11232.2 1247.4 47.3 0.6 1.6 4 14AUG98 TSO1 33 98 1 2297.2 0.2 753.6 10096.8 1201.9 45.5 0.3 1.1 5 21AUG98 TSO1 34 98 1 2254.0 0.0 615.7 10604.8 1361.2 66.9 0.1 0.6 6 28AUG98 TSO1 35 98 1 2169.1 0.0 573.3 10192.3 1226.0 41.5 0.4 0.8 7 04SEP98 TSO1 36 98 1 2960.0 0.0 760.1 11505.6 1230.3 63.8 0.1 1.8 8 11SEP98 TSO1 37 98 1 1743.2 0.0 431.1 8881.0 1263.0 50.0 0.4 3.6 9 18SEP98 TSO1 38 98 1 2283.9 0.0 484.5 11927.8 1123.4 38.8 0.2 1.7