Question:
How does Control-M Batch Impact Manager (BIM) and Control-M Forecast handle the following situation:
- The "Maybe" conditions that may or may not exist in the active environment
- The conditions that are created by externally (Orphan Conditions) and not by Control-M job in the active
- Which System Parameter will configure how Control-M Batch Impact Manager (BIM) or Control-M Forecast work if the In-Conditions that is defined in a job is not create on a specific day?
- What is AddAllOrphanCondition and what are the valid value?
 

Answer:
-   Manual or Orphan or External or "Maybe" conditions are conditions that are specified as "In-Condition" for jobs but does not exist at the time when Control-M Batch Impact Manager (BIM) or CONTROL-M/Forecast generates its estimation calculation.

- This may be because:
i. The job relies on a condition from a previous day.
ii. The job relies on a condition that has to be manually added or removed.

- Manual or Orphan or External or "Maybe" conditions or any other conditions that may not exist in the active environment and need to be added manually can be handled in 2 ways with Control-M Batch Impact Manager and Control-M/Forecast as described below:

1) Configuring Control-M/Enterprise Manager System Parameter: AddAllOrphanConditions.
-  This system parameter determines how Control-M BIM or CONTROL-M/Forecast should assume orphan conditions exist when generating estimation or forecast.
   Valid values:
   0: orphan conditions are not assumed to exist
   1: orphan conditions are assumed to exist
   2:  add according to job average start time (Default)

2) Using "What-If" function
- In case the value of AddAllOrphanConditions is changed to 0 then Forecast will show that a particular job or jobs did not run due to missing condition.
- In this case utilize the Add What If scenario to add this condition to that job in the Forecast.
- What If Scenarios allow to mock up a particular scenario and see what the impact will be to the batch flow.
- To add this scenario run the Forecast by running File > Load CONTROL-/EM Forecast.
- Once the Forecast is loaded right click the job waiting on the Maybe condition select Add What If Condition.

Additional Information:
- Following is the algorithm when AddAllOrphanConditions is set to "2 - Add according to job average start time (Default)"
1. If there is statistics for the job, add an Orphan conditions at the Average Start Time of the job
2. If there is no statistics for the job and no jobs using this Orphan Condition , the condition will be added at New Day Time
3. If there are other jobs waiting for the orphan condition, the condition will be added at Average Start Time of the first running job.

Note for Forecast: If folders/job depends on conditions that come from previous date (use any date) you should have What_if or Forecast BIM rules for these missing conditions.