Executing a Database Specification
Select a meta file definition.
rm
When you select a meta file definition a special Update Capacity Planning Meta File screen is displayed (an example is shown in Figure 3-108).
Figure 3-108. Update Capacity Planning Meta File Screen
/------------------- Update Capacity Planning Meta File ----------------------\ |Command ===> | | | |Composing CAP DB File def.: SYS - System Activity Tracking File | | | |Update type ===> INITIALIZE (INITIALIZE/UPDATE) | |Replace existing ===> N (Y/N) | |Private Capacity Planner data base cycle ===> 01 | |Update start date ===> _______ (ddmonyy) | |Number of months ===> ____ (1-9999) | |Execution mode ===> BATCH (BATCH/FOREGROUND) | | | |List updated CAP DB file contents ===> YES (YES/NO) | | | | | | | | | | | | | |Press END to invoke MICF inquiry execution to update the meta file. | |Enter CANCEL to terminate the meta file update. | |-------------------------------------------------------------------------------|
The following section describes parameters for the Update Capacity Planning File screen:
Update type
The specification for initializing or updating the Capacity Planning database file. If the meta file does not exist or if you plan to overwrite the current file, specify INITIALIZE. If you want to add to an existing file, specify UPDATE.
Note that if you specify INITIALIZE and the file already exists, all historical and forecasted observations that you previously placed in the file will be lost.
Replace existing
The specification for deleting an old file and replacing it with a new file. If you specify INITIALIZE and the file already exists, you must set this parameter to Y (YES) to delete the old version and confirm your intent to initialize and replace. Otherwise, specify N (NO).
Capacity Planner Database Cycle
The Private (or Shared) Capacity Planner database file cycle you want to use as input into the meta file update run.
Update start date
The start date for date range selection. If Start date is specified, only historical observations at least as recent as this value are included in the analysis. The discussion of the following control parameter describes the options for controlling date range selection.
Number of days/weeks/months
The maximum number of days, weeks, or months of historical observations to be included in the analysis. Note that once you specify the input file, the field name changes to reflect the time-span of the input file. When used along with the Start date parameter, several options are available for date range selection control:
- If you specify only Update start date, all historical observations at least as recent as the value specified for Update start date is selected.
- If you specify both Update start date and Number days/weeks/months, the date range for data selection begins with the specified value for Start date and extends for the specified number of days, weeks, or months.
- If you specify only Number of days/weeks/ months, the date range for data selection includes that number of days, weeks or months before the submit date.
- If you specify neither parameter, then all historical observations are selected when Update type is INITIALIZE. When Update type is UPDATE, the default is 1 for Number of days/weeks/months, based on theMICScalendar.
Execution mode
The specification for executing the meta file update. Specify BATCH to submit the meta file update as a batch job. Specify FOREGROUND to execute it immediately as an online SAS program.
List updated CAP DB file contents
The specification to execute a PROC CONTENTS and a PROC PRINT of the meta file to be executed after the database is updated. To do so, specify a Y (YES).
The
MICS database
Inquiry Execution screen shows the execution parameters that are available before the database update job is submitted for processing. This screen and its control parameters and options are discussed in detail in the Executing a File Definition Inquiry section.