SMX CtrlM is a solution for Control-M allows workload simulations and analysis of the path for different jobs of Production - predecessors and successors.
When we make efforts in the Control-M, there are always questions that do not know how to evaluate correctly:
- How are certain jobs running on a certain date?
- What was the impact of certain jobs in the daily execution and at the BATCH window itself?
- What trends can be identified in the BATCH window?
- How I can optimize my BATCH window?
Within the GANTT chart of SMX CtrlM, all jobs are displayed against a timeline and in relation to each other, allowing you to see exactly what jobs has been affected each other by a daily execution of production in particular. Timelines indicate average time of work execution, very useful to have an immediate comparison.
To calculate and display the average times of executions in the GANTT chart, SMX Ctrl-M allows the use of different statistical models based on the different types of series production. For example, the average time between runs later this month, quarterly production and the daily running.
The graphics provide the user a complete picture of each situation, showing the number of jobs running in parallel and the average CPU usage - for Control-M to Z / OS. Bottlenecks and other potential problem areas can be identified and actions to prevent these problems can be done in a proactive way.
Using historical statistics, the Gantt graphics can show:
- Simulate the effect of changes at a job.
- The dependence structure of a job.
- Identify the critical path of the work in a scheldure.
By modifying the execution times in a simulation, you can identify how changes are critical path under certain conditions. You can simulate different Production time cycles - day cycle, monthly cycle, etc.
The purpose of conducting a simulation is to determine the impact of new work or existing work if run more or less time, and see how it can affect the Batch window. For accurate workload, the simulation is performed by integrating forecasting, statistical analysis and critical path tasks within the job for Control-M.
With these powerful management functions, the former professional divination is replaced by an exact process.
Not only the route search is used to identify the known path between the start and end of operations. It can also be used to:
- To identify a full path of a predecessor job before an execution.
- To identify a full path of a successor entire branch execution.
This search can go through multiple applications and be unlimited. Optionally you can specify that the predecessor or successor to a search path is limited to a certain number of levels.