Resolution of mandatory dependencies in the current plan

In the current plan a mandatory dependency is resolved as the successor is added by dialogue, programming interfaces (PIF), event-triggered tracking (ETT), or automatic recovery (AR). When a successor that has the dependency defined as mandatory at control level (C) is added to the CP, depending on how you set the MPRESOL parameter in the JTOPTS statement, the resolution process searches for a predecessor as follows:
MPRESOL is set to NO (default) or DP
According to the resolution criteria that you set, the mandatory dependency resolution process searches for the IA time of a matching predecessor before, after, or across the IA time of the successor. When the IA time of the successor is:
Before or after the matching interval
The matching predecessor is searched within the occurrences in the current plan; if it is found, the mandatory dependency is considered resolved and a normal dependency is added to the CP. If a match is not found, the successor is flagged as mandatory pending.
Across the matching interval
The matching predecessor is searched starting from the IA time of the successor by scanning the current plan backwards to the start of the interval. If no match is found, the search continues by scanning the current plan forward, from the IA time of the successor to the end of the interval. By searching forward and finding a matching predecessor, an extra check is run for the archived completed occurrences before the IA time of the successor in order to avoid unwanted forward links (to this effect, you must have configured the BATCHOPT LTPREMSHIFT parameter so that the occurrences that completed within n days before the first uncompleted occurrence are instead kept in the new plan).

If a matching predecessor is found in the CP, the mandatory dependency is considered resolved and a normal dependency is added to the current plan. If a matching predecessor is found among the completed archived occurrences, the dependency is considered resolved and it is not added to the CP.

If no matching predecessor is found, the dependency is not resolved and the successor is flagged as mandatory pending.

MPRESOL is set to ARCHIVEDOCC
According to the resolution criteria that you set, the mandatory dependency resolution process searches for the IA time of a matching predecessor before, after, or across the IA time of the successor. When the IA time of the successor is:
Before or after the matching interval
The matching predecessor is searched first within the occurrences in the current plan; if it is found, the mandatory dependency is considered resolved and a normal dependency is added to the CP. If it is not found, the scheduler continues to search within the archived completed occurrences and if a match is found the dependency is considered resolved and is not added to the CP. If a match is not found, the successor is flagged as mandatory pending.
Across the matching interval
The matching predecessor is searched starting from the IA time of the successor by scanning the current plan backwards to the start of the interval. If no match is found, the scheduler searches for a match within the archived completed predecessors before the IA time. If no match is found, the search continues by scanning the current plan forward, from the IA time of the successor to the end of the interval. If no match is found either, the matching predecessor is searched within the completed archived predecessors after the IA time.

If a matching predecessor is found in the current plan, the mandatory dependency is considered resolved and a normal dependency is added to the CP. If a matching predecessor is found among the completed archived occurrences, the dependency is considered resolved and it is not added to the CP. If no matching predecessor is found, the dependency is not resolved and the successor is flagged as mandatory pending.

For example, operation A with an IA time at 12:00 of 27-04-2026 is defined in the database with B as external predecessor. The match is to be looked for within an absolute interval spanning from 14:00 of the day before to 16:30 of the same day of the IA time of A.

The only match that can resolve the dependency is B with IA time equal to 20:30 of 26-04-2026 that is in completed status and has been archived.

If the MPRESOL parameter in the JTOPTS statement is set to DP or NO (default), a match is not found and the successor is flagged as mandatory pending. If MPRESOL is set to ARCHIVEDOCC, a match is found with the instance of the archived completed operation B with IA at 20:30 of 26-04-2026: the dependency is considered resolved and is not added to the current plan.