Resolution of mandatory dependencies in the daily plan

When a dependency is defined as mandatory at control level (C) and a match is not found, a mandatory pending predecessor entry is created and the occurrence is set to WAITING. Because the predecessor that is required to resolve the dependency might become available later, you can have the dependency resolved during the daily plan by setting the MPRESOL parameter of the JTOPTS statement.

Based on the value that you set for JTOPTS MPRESOL the following occurs:
DP
The dependency is resolved for the successors that are flagged as mandatory pending in the LTP and for the existing mandatory pending in the CP.
Depending on 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.

If a matching predecessor is found, the mandatory dependency is considered resolved and a normal dependency is added to the CP. If no matching predecessor is found, the dependency is not resolved and the successor is flagged as mandatory pending.

ARCHIVEDOCC
The search for the dependency resolution also takes into account the archived completed occurrences. The dependency is resolved for the successors that are flagged as mandatory pending in the LTP and for the existing mandatory pending in the CP.
Depending on 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 13:00 of 24-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 18:00 of the day before to 13:30 of the same day of the IA time of A.

Two possible matches of B can resolve the dependency:
  • B with IA time equal to 20:30 of 23-04-2026 that is in completed status and has been archived.
  • B with IA time equal to 18:30 of 23-04-2026 that has not yet completed.

A match is found with the instance of B with IA equal to 18:30 of 23-04-2026: the mandatory dependency is considered resolved and becomes a normal dependency in the current plan.

At each extension, the long-term plan normally deletes all the completed occurrences that precede the first not completed occurrence (FNONC) of an application. However, if you have set JTOPTS MPRESOL(ARCHIVEDOCC) you were also required to set BATCHOPT LTPREMSHIFT(n), determining that the occurrences that completed within n days before the FNONC are archived and not deleted.