Control-M Reviews & Product Details

What works best for us is having a single monitoring view for all our batch jobs. Setting up job chains with dependencies, prerequisites, and event triggers is straightforward once you get the hang of it. We run jobs across both Linux and Windows servers, and it handles cross-platform execution well without dropping triggers. The Batch Impact Manager is also helpful for tracking SLAs and flagging delayed jobs early before they affect downstream business processing. Review collected by and hosted on G2.com.

The thick client GUI can feel heavy and slows down when you have thousands of active jobs running during peak hours. Also, the learning curve is pretty steep for new team members who aren't used to how Control-M handles conditions and quantitative resources. Upgrading agents across a large server fleet takes a lot of planning and coordination during maintenance windows, which can be time-consuming for the team. Review collected by and hosted on G2.com.

What I like most about it is its ability to reliably automate and manage complex workflows. It offers strong scheduling, monitoring, and dependency management, which makes it easier to ensure jobs run on time and that issues are identified and resolved quickly. Review collected by and hosted on G2.com.

One thing I find challenging is that it can be complex to manage and troubleshoot, especially in environments with a large number of jobs and dependencies. The interface and configuration also take some time for new users to learn and get comfortable with. That said, its strong scheduling, monitoring, dependency management, and automation capabilities still make it very valuable for enterprise workloads. Review collected by and hosted on G2.com.

What I like most about Control-M is how it brings everything together in one place. It makes it straightforward to monitor workflows, see and understand job dependencies, and quickly spot issues when something goes wrong. On top of that, the automation cuts down on a lot of manual effort and helps keep day to day operations running more smoothly. It was reliable and stable, especially when handling large numbers of jobs and complex workflows. Review collected by and hosted on G2.com.

What I dislike about Control-M is that it can feel a bit complex at first, particularly when you’re setting up and managing more complicated workflows. Some configurations take quite a few steps to complete, and troubleshooting can be time-consuming at times. The user interface could also be more modern and intuitive, which would make day-to-day navigation easier. Overall, it’s a powerful tool, but new users should expect a learning curve. Review collected by and hosted on G2.com.

Control-M has been really reliable for our batch processing. I like having everything in one place across mainframe, cloud, Hadoop, and ERP systems. The visual workflows make troubleshooting much easier, and the flexible scheduling and alerting save us a lot of manual effort. It’s not flashy, but it’s dependable and works well at scale. Review collected by and hosted on G2.com.

The biggest downside for me is the cost, especially as you scale and add more agents or features. It also has a bit of a learning curve, and the UI can feel dated in some areas. Upgrades and patching sometimes take more planning than expected, and custom reporting could definitely be more flexible. Review collected by and hosted on G2.com.

It's a Mainframe jobs' Scheduling and monitor tool, but it works right within the mainframe through the regular old green screens, so I don't have to switch between systems. It's easy for me to use and fits naturally into our secure setup.

It connects well with other systems too, not just mainframe jobs, but distributed systems and file transfers as well which helps in my quick job's flow and its dependencies. So I get one place to track everything.

It performs well even when hundreds of jobs run during peak overnight batch cycles which process high Business logics. I can quickly see what ran, what triggered it, and what's next(dependencies), which makes troubleshooting fast and helps with daily Processing

Support has been reliable, with regular updates from BMC. I've also noticed newer versions adding AI features like predictive alerts, which is a good step forward. But we are exploring these features and trying to integrate with our systems.

And what impresses me most is that mainframe technology is almost 60 years old, and it's still running strong today - with Control-M playing a big part in keeping it going smoothly. Review collected by and hosted on G2.com.

Licensing and pricing are a real pain point. It isn’t cheap, and the cost adds up as we scale to more jobs, so only a few people end up having access to this tool. Also, the GUI can feel a bit dated compared to newer tools like TWS which I have been using it as well for other Projects. Review collected by and hosted on G2.com.

What I like best about Control-M is its ability to automate, schedule, and monitor SAP BODS jobs efficiently. During my time at HCL Technologies, I used Control-M to manage job execution, monitor workflows, track job statuses, and troubleshoot job failures. Its centralized monitoring, dependency management, and alerting features helped ensure smooth execution of ETL workflows and timely data processing. Review collected by and hosted on G2.com.

One area for improvement in Control-M is that its interface and configuration can be complex for new users. Troubleshooting job failures involving multiple dependencies can sometimes take time, and setting up schedules and dependencies may require additional effort. A more intuitive interface and simpler configuration options would improve the overall user experience. Review collected by and hosted on G2.com.

I like that Control-M lets me monitor all our jobs in one place, see their status on one screen, quickly find failed jobs, and rerun them with a few clicks. The scheduling is flexible, handles job dependencies well, and makes it simple to set jobs to run automatically at the right time and in the right order. It cuts down on manual job running and failures from jobs running in the wrong order, helps me spot problems faster, and means less night and weekend work. I can monitor every job, and it helps important reports and data loads finish on time. I also find it reliable, and I like the alerts and notifications, that it works with many systems, and the support. Getting started as a user was fairly easy after some basic training. Review collected by and hosted on G2.com.

I find the user interface old and confusing because it has too many options. New users need time to understand it. The licensing is expensive, and the screen can be slow when loading many jobs. Sometimes error messages and logs are hard to understand, and setup, installation, or upgrades take effort. Review collected by and hosted on G2.com.

Control-M makes complex workflows much easier to manage. Its biggest strength is the ability to orchestrate jobs across multiple platforms and applications from a single interface, which saves a lot of time and reduces errors. The scheduling is highly flexible, letting you set dependencies and triggers so processes run exactly when they should.

Another upside is the visibility and monitoring tools—you can track jobs in real time, quickly identify bottlenecks, and get alerts before issues escalate. This helps improve reliability and ensures critical business processes run smoothly.

Finally, Control-M integrates well with cloud services and modern technologies, so it’s not just limited to traditional batch jobs. That adaptability makes it a long-term solution for organizations evolving their IT environments Review collected by and hosted on G2.com.

Levels of support that acts as too tough to reach out. Needed proper follow up with documented communication. Immediate response with quick solution needed. Review collected by and hosted on G2.com.

I like Control-M’s centralized job scheduling and monitoring because I can manage multiple jobs and workflows from one platform. I can track job status in real time, see how workflows are running, and identify failures or delays without checking each system manually. It manages dependencies so tasks run in the right sequence, and its automation reduces manual effort, improves reliability, and helps critical processes run smoothly and on time. Using it with application systems, databases, and monitoring tools also gives me better visibility into job performance and helps me resolve failures efficiently. From a user perspective, the initial setup was relatively straightforward, and scheduling jobs, monitoring workflows, and managing dependencies became easier once the environment was configured. Review collected by and hosted on G2.com.

I find the user interface and navigation could be more intuitive. Troubleshooting failed jobs can take additional investigation, and error messages could explain the root cause more clearly. I’d also like better alert customization, reporting, and integration with other monitoring tools. The initial configuration and integration required technical expertise, and some documentation and configuration steps could be more user-friendly to make onboarding easier for new users. Review collected by and hosted on G2.com.

I like how reliably Control-M handles complex dependencies. I can visualize entire workflow chains and know downstream jobs won’t trigger until prerequisite steps succeed, which gives us peace of mind. It rarely fails silently, and its stability is exceptional. Having everything in one unified dashboard has cut down our mean time to resolution. We can see which step failed and why, then restart from the point of failure with one click, saving us hours of manual troubleshooting. Setup was relatively smooth, and the documentation and best practices helped us configure the central server and agents without major blockers. I find Control-M rock solid and good at managing mission-critical workloads and complex tasks. Review collected by and hosted on G2.com.

I find the learning curve for new team members quite steep. The desktop client feels a bit dated and dense with menus, so onboarding people who haven’t used enterprise scheduling tools takes time. A more modern, simplified web UI would make everyday navigation faster. Setup was relatively smooth, but it was enterprise-level in scope, and mapping our legacy scheduling and permissions took the main effort. Review collected by and hosted on G2.com.