What is most valuable?
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!
How has it helped my organization?
Previous scheduling solutions were platform specific, so when the overnight batch processes crossed between technologies, manual intervention was required. This was time costly and meant that it was not possible to get an overall picture of the flow/progress.
What needs improvement?
The ability to work offline would be an improvement. It is sometimes inconvenient that you cannot load and work on a schedule – unless you are connected to a Control-M Server. For example, when you are away from the office or on a train…
When you launch the application, the first thing that you need to do is 'log in' to a valid Control-M server. It would be nice if there was an 'offline' mode that would enable you to launch the application and then work on a batch schedule that can be 'checked in' to the appropriate server when you are next connected. This would enable users to be productive in environments where there is not a reliable network connection.
For how long have I used the solution?
I have been working with Control-M for 20 years, using many versions; three years with version 8.
What was my experience with deployment of the solution?
What do I think about the stability of the solution?
I have not encountered any stability issues.
What do I think about the scalability of the solution?
I have not encountered any scalability issues.
How are customer service and technical support?
Technical support is sufficient. BMC have a group of specialists in Tel Aviv who will advise on the best solution to any issue. It can be a little painful, trying to send huge log files to the vendor, but they are very helpful.
Which solution did I use previously and why did I switch?
I have had limited experience with Windows Task Scheduler, Cron and Autosys. These are very basic scheduling tools that do not offer anywhere near the functionality of Control-M.
How was the initial setup?
Out of the box, most clients will be fine installing Control-M with all default options. You have a choice of the packaged PostgreSQL database solution, or you can opt to use MS SQL It is therefore a relatively simple setup.
What's my experience with pricing, setup cost, and licensing?
Control-M is expensive, but you get what you pay for. Talk to your account manager and discuss licensing options.
Which other solutions did I evaluate?
Before choosing this product, I did not evaluate other options.
What other advice do I have?
Which version of this solution are you currently using?