External dependencies between multiple occurrences
If you specified an external dependency, HCL Workload Automation for Z must decide which occurrences of the applications should be linked by the dependency relationship. This is not always obvious, because there might be several occurrences of each application in the LTP and current plan. The relationship is set up (in other words, the dependency is resolved) by HCL Workload Automation for Z during the LTP planning process.
To resolve an external dependency, HCL Workload Automation for Z considers the IA time specified at the successor operation level and the IA time specified at the occurrence level of each potential predecessor. If an IA time is not specified at successor operation level, the IA time specified at the successor occurrence level is used instead. Considering that the operation IA time might have been specified not only to resolve dependency but also to set a time dependency or affect the planning start time, you can choose to use always the occurrence IA time for dependency resolution by setting the appropriate value in the JTOPTS(OPIADEP) parameter.
For an explanation of input arrival times, see Specifying the input arrival time and Specifying times, actions, and alerts for operations. The criterion followed to pick the predecessor input arrival time which resolves the dependency is defined in the DEPENDENCY RESOLUTION CRITERIA panel described in the next section.
HCL Workload Automation for Z resolves external dependencies during the LTP planning process. If you manually change the input arrival time of an occurrence, or an individual operation, in the LTP or current plan (for example, using the panels), this change does not affect dependencies that have already been resolved. To change the dependency relationships for occurrences that are already scheduled, you must explicitly modify them.