Control-M has a huge number of features and utilities that assist users in monitoring their schedules, and developers to build schedules that interface with many technologies. Here are some that stand out:
- Cross-platform support. A Linux job can be dependent on a Windows job, which can be dependent on many other flavours of hardware/software. Your batch is therefore managed by a single tool, allowing you to monitor your entire flow.
- Great GUI. Easy to navigate. Customisable. Status at a glance.
- BIM (Batch Impact Manager). Proactively monitors a batch flow, against a pre-defined OLA/SLA and alerts as soon as an exception occurs that might threaten the target.
- Automated error handling. Depending on the exit status of a process, automated actions can be defined that might circumvent the need to callout.
- Forecast utility. Particularly useful after making changes to a batch flow, to see what impact those changes will have.
- Reporting utility. Generate reports for the business to track batch performance, usage, and so on.
- Mobile App. Business users can track the progress of their own batch flow, on the go.
- Control Modules. These allow you to define jobs that interface with databases, SFTP, SAP, and so on, directly, via secure connection profiles.
- Too many great features to list!
Solid review Mr. Dean Tuson and great to see it was you as the reviewer. Hope all is well in life.
I believe BMC could provide greater analytical tools for the User and their organization, specifically in the area of "historical" analytics. The existing toolsets they offer are great for predicting the impact of proposed changes to the jobstream flow and their ability to predict expected endtimes of SLAs (real-time, using BIM), yet I always thought they missed the boat on analyzing Batch after completion (i.e. last night's Batch, the past week, month, year).
I want to go back and find out why Ive missed my SLA so often in the past, find out what the bottlenecks actually we're, what was in the "critical path" that contributed to the breach of SLA (i.e. longest running jobs in the critical path, repeat job failures in the path, delays due to Priority and/or Quant Resources....
Very powerful to know AND act upon such analysis to bring enhancement to those problematic areas of the path, that result in completing stated SLAs earlier to the Business Users.
Aside from that, I believe BMC could improve in use of Web based GUI and move away from the existing solution and use of supporting applications like Citrix to deliver the GUI to larger User bases...
And that's a wrap !