AddAllOrphanConditions

Enables you to add external or orphan conditions.

Manual conditions are specified as In Conditions for jobs but do not exist at the time Batch Impact Manager estimates the completion time of the services and jobs. This may be because:

• The job relies on a condition from a previous day.
• The job relies on a condition that has to be manually added.

Valid values:

• 0- Do not add conditions.
• 1- At conditions at New Day.
• 2- Add conditions at the average start time of the first job waiting for the condition.

Default: 2

AddVirtualOrphanConditions

Ignores delete conditions if needed by other jobs and there are no other jobs that add them.

Valid values:

• 0: All delete conditions are performed
• 1: Delete conditions are not performed if there are no jobs in the same Control-M
• 2: Delete conditions are not performed if there are no jobs in all Control-M/Servers
• 4: Almost all delete conditions are ignored

Default: 0

AlertConsolidationMode

Determines whether the BMC Batch Impact Manager consolidates email alerts, BMC Remedy ITSM incidents, and shout messages.

Valid values:

• 0- Disables consolidation.
• 1- Alerts are consolidated in one line with some exceptions regarding alerts recorded in separated lines and or with added spaces.
• 2- Alerts are consolidated with a space between the message text for each service.

Default: 1

AllowReportViewing

Allows service report viewing from web for users that are not administrators.

Valid values: The number 1

Default: 0

BackupGUIServers

GUI Servers to use in case there is a problem with the primary GUI Server (as indicated in the Control-M Configuration Manager). The value of this parameter can be one GUI Server or list of GUI Servers separated by commas ( , ).

Valid values: String expression.

BIMUserName

The user name that Batch Impact Manager uses when connecting to Control-M/EM.

Valid values: bimuser

Default: bimuser

NOTE: Before changing this value, ensure that the new user name value already exists in Control-M/EM. (If it does not exist, create it before changing the value.) The Batch Impact Manager user name is a hidden user, so if a new user name is indicated here it will also become hidden.

ConditionDaysToLoad

Defines the number of days of active conditions Batch Impact Manager loads for service calculations.

Valid values: The number of days equal to or greater than 1 .

Default: 7 days

ConnectToGsrRetryDelay

The delay, in seconds, Batch Impact Manager waits before reconnecting to the Control‑M/EM GUI Server, if the connection has failed.

Valid values: Any whole number equal to or greater than 1.

Default: 30

DateFormat

Format in which dates are displayed in BIM alert messages.

Valid values: DD/MM and MM/DD.

Default: DD/MM

DefaultAverageTime

Average run time for jobs with no statistics. In the format HH:MM. This value is often used if no statistics are available.

Valid values: Time in the format of HH:MM.

Default: 00:05

DetectProblemsInterval

Interval at which Batch Impact Manager checks for problems in the service.

Valid values: Time in the format of HH:MM:SS.

Default: 00:01:00

DiscardOrphanConditions

Ignores missing conditions if it relates to an OR condition.

Valid values:

• 0: Add all conditions
• 1: Ignore OR conditions if missing.

Default: 1

EmailSender

Valid values: E-mail address from which alerts are being sent.

Default: bim@bmc.com

EmailServer

Defines the E-mail server and port that is used to send alert notification emails. This value must be set after installation.

Format: <server host>[:<port number>]

Default: mail

If the port is not specified, the default is 25.

ExecuteConfirmedJobs

Enables you to execute jobs that are waiting confirmation.

Valid values:

• 0: Do not execute jobs
• 1: Execute at New Day
• 2: Execute at the job’s average start time

Default: 0

FailoverMaxRetry

Maximum number of times the Batch Impact Manager Server should reconnect to the Control‑M/EM GUI Server, if this connection repeatedly fails. This parameter is reset by the FailoverMinUptime parameter.

Valid values: Any whole number equal to or greater than 1.

Default: 10

FailoverMinUptime

The amount of time that the Batch Impact Manager Server must be connected to the Control M/EM GUI Server, before the counter used by the FailoverMaxRetry parameter is reset to zero. For example, if this value is 30 minutes and the connection has been maintained for more than 30 minutes, the counter is reset.

Valid values: Time in the format of HH:MM:SS

Default: 00:30:00

JobNameMode

The field is used to identify a job in Control-M. Batch Impact Manager uses this parameter when processing the PROBLEMATIC‑JOBS auto edit variable.

Valid Values:

• 1. JOBNAME/MEMNAME- Search according to the name of the job or the member.
• 2. JOBNAME- Search according to the name of the job.
• 3. MEMNAME- Search according to the name of the member.

Default: JOBNAME/MEMNAME

MailCorrectionMessage

Defines the correction message of a problematic service that has become OK.

Valid values: String expression.

MaxNumDetectThreads

Maximum number of threads for recalculating the status of the service.

Valid values: Any whole number equal to or greater than 1.

Default: 2

MaxNumOfVpsWithScenario

Determines the maximum number of Analysis ViewPoints with What-If scenarios that can be opened simultaneously.

Default: 3

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.

Valid values: Any whole number equal to or greater than 1.

Default: 2

MinGapToJobParents

Determines the minimum interval (in seconds) between jobs reported as the gap.

Default: 60

NewJobsInterval

Interval at which Batch Impact Manager will check to see if new jobs have been added to the critical service.

Valid values: Time in the format HH:MM:SS.

Default: 00:01:00

NumberOfReportDays

NOTE: Determines the number of days to keep report data in the database for generating reports about services.If you update this parameter, you need to update this same parameter with type general.

Valid values: The number of days equal to or greater than 1

Default: 90

PrevDaysCyclicOnly

Determines if the parameter PrevDaysOrphanConditions is for Cyclic jobs or for all jobs.

Valid Values:

• 0: All jobs are affected by PrevDaysOrphanConditions
• 1: Only cyclic jobs are affected by PrevDaysOrphanConditions

Default: 0

PrevDaysOrphanConditions

Determines the number of previous ODATs not to raise Orphan conditions

Valid Values:

• 0: All jobs from all ODATs are submitted in the Simulation by BIM.
• 1: All Orphan conditions, that the jobs waiting for this condition are of an ODAT that is 1 day or more prior to the CTM Server ODATwill not be raised, so the jobs waiting for this condition, will not run.

Default: 0

SendMailCorrectionMessage

Determines whether to send the correction message or not.

Valid values:

• 0: Do not send
• 1: Send

Default: 1 (send)

SupportWorkLoadResources

Determines if load balancing of quantitative resources is supported.

Valid values:

• 0: Not supported
• 1: Supported

Default: 1

UseDoCondition

Add conditions created by On Do Actions.

Valid values:

• 0: Do not add conditions
• 1: Add only added conditions
• 2: Add added and deleted conditions

Default: 1