System variables influence the behavior of BMC CONTROL-M/Forecast components and features. Table 29 describes the function of each BMC CONTROL-M/Forecast -related system parameter and lists its default, if one exists.
BMC CONTROL-M/Forecast administrators can change the value of most of these system parameters. If, however, a system parameter is to be modified only upon instruction of Customer Support, this is noted in the description of that system parameter.
System parameters are modified using the System Parameters window of the CONTROL-M Configuration Manager. To learn how to modify a system parameter, see the working with system parameters topic in the CONTROL-M Administrator Guide.
NOTE
After modifying any of these system parameters, you must stop and restart the BMC Batch Impact ManagerServer.
Table 29 Forecast parameters (part 1 of 3) System parameter Description
AddAllOrphanConditions Manual conditions are conditions that are specified as in conditions for jobs but will not exist at the time BMC CONTROL-M/Forecast generates its forecast. This may be because:
■ The job relies on a condition from a previous day. (Forecasts are only generated for a specific day.)
■ The job relies on a condition that has to be manually added or removed.
This system parameter determines if, by default, BMC
CONTROL-M/Forecast should assume orphan conditions exist when generating forecasts.
Valid values:
■ 0: orphan conditions are not assumed to exist
■ 1: orphan conditions are assumed to exist at newday.
■ 2: Orphan conditions are added at the average start time of the first job waiting for the condition. (Default)
AllowQueryFieldValues Determines whether the drop-down lists of available values are displayed for fields in the What-If event definition dialog boxes.
Valid values:
■ 0 – drop-down lists are not displayed
■ 1 – drop-down lists are displayed (Default)
AvgRunInfoHistory Sets the number of historical samples used as a basis when calculating the average runtime for reporting purposes. Default: 20
Configuring BMC CONTROL-M/Forecast using system parameters
DefaultAverageTime Average run time for jobs with no statistics. In the format HH:MM. This value is often used if no statistics are available. Default: 00:05.
DeleteChunkSize Determines the number of records deleted in one transaction by the purge_runinfo utility when removing run information from the RUNINFO_HISTORY table in the CONTROL-M/EM database.
Default: 10000.
ExecuteConfirmedJobs Determines if, by default, BMC CONTROL-M/Forecast should assume all jobs are confirmed.
Valid values:
■ 0 - all jobs are not confirmed (Default)
■ 1 - all jobs are confirmed at new day time.
■ 2 - all jobs are confirmed at the job’s average start time.
IgnoreDeviationSampleCount Defines how many expeceptional historical samples should be ignored when calculating the average runtime for reporting purposes. Default: 2 MaxDailyRerunInfo Defines the number of runs per day the gateway will keep in the history
table for each job. Default: -1 (No limit)
MaxForecastJobsInMem Maximum number of jobs that should be retained in memory at a time on each BMC CONTROL-M/Forecast Server. BMC CONTROL-M/Forecast Server releases all memory after the forecast is closed in
CONTROL-M/Desktop. Default: 200000
Note: This system parameter does not affect forecasts of schedules or reporting.
MaxForecastRunningRequests Maximum number of forecast requests that can run simultaneously.
Default: 5
max_futureplan_cb_seq_size Sets the minimum chunk size for jobs when generating the forecast.
Default: 1000
MaxSimulationDays Number of days to simulate the running of the services to calculate estimated end times. Each additional day takes more CPU time during the calculation process. Default: 2
RunInfoStatsPurgeDays Sets the number of days that job runtime statistics, which have not been updated, are retained in the database.
Default: 100 days
RunInfoStatsPurgeInterval Sets the number of minutes between purges of obsolete job runtime statistics.
Default: 30 minutes
Note: A value of 0 prevents purging.
RunTimeHistoryDays Sets the number of days historical statistics should be saved for reporting purposes.
Default: 90 days
ScenarioMaxSize Maximum size (in KB) of the XML files that hold forecast What-If scenarios.
Default: 64 Table 29 Forecast parameters (part 2 of 3)
System parameter Description
Configuring BMC CONTROL-M/Forecast using system parameters
SimulatorEngineStep Interval, in seconds, the simulation advances its calculation of the estimated end time.
Valid values:
■ 1 - Improves accuracy.
■ 10 - Default
■ 60 - Improves performance
upd_progress_interval_sec If BMC CONTROL-M/Forecast should send updates when loading a forecast. Valid values are:
■ 0 - No
■ 1 - Yes (Default)
UserDailyCmdRegexp Regular expression that identifies Command-type jobs that use the ctmudly user daily job to order tables. If the command specified in the Command field in a job editing form matches the expression, BMC
CONTROL-M/Forecast assumes that the job uses ctmudly.
Default: ^.*ctmudly[^ ]*
Note: The regular expression, ^.*ctmudly[^ ]*, identifies jobs that call ctmudly, regardless of the specified path or file extension.
UserDailyFileNameRegexp Regular expression that identifies Job-type jobs that use a particular user daily job (usually ctmudly) to order tables. If the name specified in the File Name field in a job editing form matches the expression, BMC
CONTROL-M/Forecast assumes that the job uses the user daily.
Default: ^.*ctmudly.*
Note: If you use this system parameter, you must also use the UserDailyParamNO system parameter so that BMC
CONTROL-M/Forecast can access the name of the user daily.
UserDailyParamNO Numeric suffix of the AutoEdit variable, %%PARAMn, which contains the name of the user daily. For example, if this system parameter is set to 2, BMC CONTROL-M/Forecast reads the name of the user daily from
%%PARAM2.
Default: 1 Table 29 Forecast parameters (part 3 of 3)
System parameter Description