Path analysis allows you to determine, amongst other things, what the effect of a change may be to any particular job within a job dependency structure.
The visualjob for Control-M path analysis feature allows users to search for the path of Control-M jobs between known start and end points, the predecessor dependency path branching to a job or the successor dependency path branching from a job.
Optional path search criteria allow finding a path within those jobs which are planned for execution on a particular day in the future or allow finding all paths or even the critical path within those jobs that have been executed on a particular day in the past. The path analysis is not limited to one Control-M environment. Paths between Control-M for z/OS and Control-M jobs running multiple Control-M servers are identified.
The visualjob for Control-M path analysis can be further fine tuned while considering or ignoring different types of dependencies, like conditions from type “static” or “previous” or post processing conditions.
These enhanced path search analysis options provide more accurate, compact and precise answers to better understand your Control-M job net.
The result set of a found path is clearly displayed in the visualjob for Control-M WebView flowchart. All jobs, which do not belong to that path, can optionally be hidden.
This Control-M dependency analysis often forms the necessary basis for extended run time analysis, simulations, path optimization or re-engineering activities with the visualjob for Control-M Workload Analysis and Workload Simulation functions. The Workload Simulation function also includes the Critical Path Simulation for Control-M.