JES Spool Activity (Resource Element Files)
Use the
MICS Capacity Planner
to create a resource element file for tracking the print load of remote printers.micsrm140cd
Problem Description
For this case study, a resource element file was created to track the print load of seven remote printers for a shared spool JES2 installation.
The remote printers that are used in this study are listed below:
Remote Number | Location |
0 | Computer Center, JES LOCAL |
12 | Engineering |
34 | Systems Programming |
80 | Tech Services |
91 | Production Control |
93 | Refinery |
96 | Application Development |
The case study addresses the following areas:
- Summarizing multiple ZONEs and SYSIDs
- Using a selection macro to limit the volume of data processed by the program. Rather than summarizing the data for all the remote printers, a selection macro excludes observations for remote printers other than the seven being considered in the study.
Control Parameters
Figures 3-57 through 3-68 show the control screens that we used to create and execute this resource element file example.
Figure 3-57. 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.: JES - JES Spool Example | | | |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 ===> N (Y/N) | --------------------------------------------------------------------------------
The specifications on the Resource Element File Definition screen that is shown in Figure 3-57 do the following:
- Set the primary summarization to MONTHS
- Set the secondary summarization to ZONE
Figure 3-58. Specifying Common Data Selection
/-------------------------- Resource Element File ----------------------------\ |Option ===> 1 | | | |Composing CAP DB file def.: JES - JES Spool Example | | | | | | 1 - Insert Common Data Selection | | Specify data selection criteria to apply to ALL files. | | 2 - InsertMICSFile and Data Element Selection | | Select aMICSfile 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 that is shown in Figure 3-58.
Figure 3-59. 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.: JES - JES Spool Example | | | | | |SYSID ===> TSO1 TSO2 ____ ____ ____ ____ ____ ____ ____ ____ | | ____ ____ ____ ____ ____ | | | |Zone ===> _ _ _ _ _ _ _ _ _ (1 - 9) | | | |Hour ===> __ - __ __ - __ __ - __ __ - __ __ - __ (0 - 23) | | | |Dayname ===> _________ _________ _________ _________ _________ | | | | | | | | | | | | | | | | | |Specify common data selection SAS statements ===> Y (Y/N/R) | --------------------------------------------------------------------------------
The Common Data Selection screen that is shown in Figure 3-59 specifies that observations with SYSIDs that are equal to TSO1 or TSO2 are to be included in the resource element file. SAS statements are specified to further control data selection.
Figure 3-60. Selecting Common Data
/-------------------------- SAS System Statements --------------------------\ |Command ===> Scroll ===> CSR | | | |Inquiry Step: File & Data Element Sel.: JES - JES SPOOL | | | |SAS Statements for the SELECT Macro | |------------------------------------------------------------------------------| |****** ***************************** TOP OF DATA *****************************| |==MSG> SPECIFY SAS STATEMENTS TO SUBSET THE CAPACITY PLANNING DATA BASE FILE. | |=NOTE= %MACRO SELECT; <=== PLEASE DO NOT PLACE LINES BEFORE THIS LINE. | |000001 IF ROUTE = 000 OR ROUTE = 012 OR ROUTE = 034 OR | |000002 ROUTE = 080 OR ROUTE = 091 OR ROUTE = 093 OR | |000003 ROUTE = 096 ; | |=NOTE= %MEND SELECT; <=== PLEASE DO NOT PLACE LINES AFTER THIS LINE. | |****** **************************** BOTTOM OF DATA ***************************| | | --------------------------------------------------------------------------------
The SAS Statements screen in Figure 3-60 shows the route code values that were selected to be included in the resource element file.
Figure 3-61. Selecting
MICS
Files and Data Elements/--------------------------- Resource Element File ---------------------------\ |Option ===> 2 | | | |Composing CAP DB file def.: JES - JES Spool Example | | | | | | 1 - Insert Common Data Selection | | Specify data selection criteria to apply to ALL files. | | 2 - InsertMICSFile and Data Element Selection | | Select aMICSfile and data elements. | | 3 - Insert Cross-File Data Element Definition | | Specify cross-file data element derivations. | | | | | | | | | | | | | | | | | | | | | | | --------------------------------------------------------------------------------
Option 2, Insert
MICS
File and Data Element Selection, is chosen on the Resource Element File screen that is shown in Figure 3-61.The
MICS
File and Data Element Selection screen that is shown in Figures 3-62 and 3-63 specifies that the MICS
SPL 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. User-defined logic is to be supplied via one of the MICS
file processing exits.Figure 3-62./--------------------MICSFile and Data Element Selection Screen - Screen 1MICSFile 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.: JES - JES Spool Example | |MICSfile ===> SPL (fff) - BATCH USER SPOOL ACTIVITY FILE | |Input Time-Span ===> MONTHS (DETAIL/DAYS/WEEKS/MONTHS) | |Data base (s) ===> P | |Include CAPAPUs ===> N (Y/N) -------Line Commands--------| |Summarize file by ===> ROUTE___ | 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 | | - -------- ----------------------------- - ---- ---- ----- --- ------------- | | _ ROUTE Route Number | | D RET N 050 5 _____________ | | _ DATE Interval End Date | | _ RET D 000 7 DATE7________ | | _ MONTH Month of Year | | _ RET N 000 2 _____________ | | _ RMTLOCLR Local Print Lines | | _ ACCM N 120 7 _____________ | | _ RMT012LR Remote 012 Lines | | _ ACCM N 120 7 _____________ | | _ RMT034LR Remote 034 Lines | | _ ACCM N 120 7 _____________ | |******************************* BOTTOM OF DATA *******************************| | | --------------------------------------------------------------------------------\
Figure 3-62.
MICS
File and Data Element Selection Screen - Screen 2/--------------------MICSFile 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.: JES - JES Spool Example | |MICSfile ===> SPL (fff) - BATCH USER SPOOL ACTIVITY FILE | |Input Time-Span ===> MONTHS (DETAIL/DAYS/WEEKS/MONTHS) | |Data base (s) ===> P | |Include CAPAPUs ===> N (Y/N) -------Line Commands--------| |Summarize file by ===> ROUTE___ | 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 | | - -------- ----------------------------- - ---- ---- ----- --- ------------- | | _ RMT080LR Remote 080 Lines | | _ ACCM N 120 7 _____________ | | _ RMT091LR Remote 091 Lines | | _ ACCM N 120 7 _____________ | | _ RMT093LR Remote 093 Lines | | _ ACCM N 120 7 _____________ | | _ RMT096LR Remote 096 Lines | | _ ACCM N 120 7 _____________ | | _ SPLNLR Logical Writer | | D ACCM N 050 13 _____________ | | _ SYSID System Identifier | | _ RET A 000 4 _____________ | --------------------------------------------------------------------------------
Figure 3-63.
MICS
File and Data Element Selection Screen - Screen 3/--------------------MICSFile 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.: JES - JES Spool Example | |MICSfile ===> SPL (fff) - BATCH USER SPOOL ACTIVITY FILE | |Input Time-Span ===> MONTHS (DETAIL/DAYS/WEEKS/MONTHS) | |Data base (s) ===> P | |Include CAPAPUs ===> N (Y/N) -------Line Commands--------| |Summarize file by ===> ROUTE___ | 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 | | - -------- ----------------------------- - ---- ---- ----- --- ------------- | | _ YEAR Year of Century | | _ RET N 000 2 _____________ | | _ ZONE Time Zone | | _ RET A 000 1 _____________ | |******************************* BOTTOM OF DATA *******************************| | | --------------------------------------------------------------------------------
Figure 3-64.
MICS
File Processing Exits Menu/----------------------MICSFile Processing Exits Menu -------------------\ |Command ===> | | | |Inquiry Step: File & Data Element Sel.: SPL - BATCH USER SPOOL 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) | | | | | | | | | | | | | | | | | | | | | --------------------------------------------------------------------------------
The
MICS
File Processing Exits Menu that is shown in Figure 3-64 indicates that the data element derivation logic is to be defined by the user.Figure 3-65. Selecting File-Unique Data
/-------------------------- SAS System Statements ---------------------------\ |Command ===> Scroll ===> CSR | | | |Inquiry Step: File & Data Element Sel.: JES - JES SPOOL | | | |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 ROUTE = 000 THEN RMTLOCLR + SPNLR ; | |000002 IF ROUTE = 012 THEN RMT012LR + SPNLR ; | |000003 IF ROUTE = 034 THEN RMT034LR + SPNLR ; | |000004 IF ROUTE = 080 THEN RMT080LR + SPNLR ; | |000005 IF ROUTE = 091 THEN RMT091LR + SPNLR ; | |000006 IF ROUTE = 093 THEN RMT093LR + SPNLR ; | |000007 IF ROUTE = 096 THEN RMT096LR + SPNLR ; | |=NOTE= %MEND CAPSMRY; <=== PLEASE DO NOT PLACE LINES AFTER THIS LINE. | |****** **************************** BOTTOM OF DATA ***************************| | | --------------------------------------------------------------------------------
The SAS Statements screen in Figure 3-65 shows the SAS statements that are used to subset the input data to ROUTEs under consideration only, and to derive new data elements to hold the values for the number of print lines for each of the remote printers of interest.
Figure 3-66. Validating the Inquiry
/--------------------------- Resource Element File --------Inquiry Validated.-\ |Command ===> Scroll ===> CSR | | | |Composing CAP DB File def.: JES - JES Spool 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.: SPL - BATCH USER SPOOL ACTIVITY FILE | |****************************** BOTTOM OF DATA ********************************| | | | | | | | | | | | | | | | | --------------------------------------------------------------------------------
After the resource element file definition parameters are specified, the Resource Element File is used to validate the inquiry. Figure 3-66 shows this screen after VALIDATE is typed at the Command prompt.
Figure 3-67. Saving the Inquiry
/----------------------- Update Capacity Planning File -------- Confirm Save.-\ |Command ===> | | | |Modifying CAP DB File def.: JES - JES Spool 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 screen that is shown in Figure 3-67 is used to save the inquiry so that it can be executed.
Figure 3-68. Executing the Inquiry
/----------------------- Update Capacity Planning File -------------------------\ |Command ===> | | | |Composing CAP DB File def.: JES - JES Spool Example | | | |Type of update ===> INITIALIZE (INITIALIZE/UPDATE) | |Replace existing file? ===> N (Y/N) | | | |Input data source ===> ONLINE (ARCHIVE/ONLINE) | |MICSfile cycle(s) ===> 01 - 05 (0 - 99) | |Archive generation number ===> ___ (0 to -99) | | | |Starting date of update ===> _______ (ddmonyy) | |Number of months to select ===> 5___ (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 5 are specified as input to the database loading process on the Update Capacity Planning File screen that is shown in Figure 3-68. The updated resource element file will be printed after the update is complete.
Output Report
The following figure 3-69 Resource Element File Contents Report shows the output that is created by the PROC PRINT of the updated data set.
MICSCapacity Planner OBS DATE MONTH SYSID YEAR ZONE RMTLOCLR RMT012LR RMT034LR RMT080LR RMT091LR RMT093LR RMT096LR 1 31MAY98 5 SPOL 98 A 170892378 1878785 257370 120771 17080144 9607193 3464558 2 30JUN98 6 SPOL 98 A 181624570 1803782 440657 126215 13941631 9232379 2415886 3 31JUL98 7 SPOL 98 A 178294112 1637214 418027 101766 15656930 10687353 1799042 4 31AUG98 8 SPOL 98 A 183922396 1828908 541960 117295 7790766 8053527 392477 5 30SEP98 9 SPOL 98 A 174622520 502184 62965 3468 2071539 1723890 109273