Control-M Reviews

My main use case for Control-M is that my team is in charge of all the alerting and monitoring, as well as the scheduling and creation of all schedules within Control-M.

The scheduling my team creates with Control-M serves all the IT audience within the company, so we have a mix of everything. Any need from developers, database administrators, or anyone from the infrastructure or development teams is handled, such as transferring files or updating databases. We deal with all requests within the company related to scheduling.

Within my team, we have around 10 people using Control-M who are focused on monitoring and reacting to alerts, as well as creating all schedules and doing all scheduling work. Beyond that, we have developers, DBAs, and others who check Control-M to review the performance of their jobs and logs. We have around 50 people total, though I don't know the exact number.

The best features Control-M offers are the stability and ease of use.

The interface of Control-M is easy to use and it is a very stable and reliable application. Control-M has a very high positive impact on my organization as it is a reliable tool that is very stable. We usually don't have issues related to the application itself, so there is a very high impact.

Control-M can be improved by including more options for automating things from an alerting handling perspective.

Reporting features are a field that we would like to have more statistics about, including jobs, usage, and errors. We definitely would also like to have more options to integrate Control-M with other applications such as JSM, ServiceNow, OmniCenter, or other monitoring tools that can provide information from Control-M. There is always room for improvement for any application.

It is easy in theory, but I find it challenging to integrate Control-M with technologies for my data ops and DevOps processes as changes occur. There have been a few efforts to integrate Control-M with other applications like Ansible, JSM, and OmniCenter, and it has been very challenging. From a DevOps perspective, I am not aware of any efforts, so I don't have information about that. However, related to the ones that I mentioned, it has been very challenging because there are not many options to integrate with Control-M. I'm not sure if this is due to a lack of training or application knowledge from our side or if it is something that the application itself is not providing.

I have been in my current field for 20 years.

Control-M is stable.

Its scalability is challenging.

Control-M has very good customer support.

We don't have a metric for return on investment from a Control-M perspective. We are expecting to see some of that if at some point Control-M starts integrating AI features and AI functions into the application.

The biggest lesson I have learned from using Control-M is the importance of having a reliable and stable scheduler.

My advice for others looking into using Control-M is that training is key to learning how Control-M works behind the scenes and in the scheduling part. I also advise looking for stability and implementing the HA environment.

I would rate Control-M an eight on a scale of one to ten.

I have been using Control-M for one and a half years.

Control-M handles enterprise-level data properly through a ground-up design. It features a distributed architecture with lightweight agents that decouple the load. The server handles overarching scheduling logic, policies, and dependencies, while Control-M agents execute and distribute workloads across local servers and cloud environments, enabling horizontal scaling.

When workload grows from thousands, capacity can be simply deployed on additional agents or containerized agents. This prevents the central server from becoming a performance bottleneck. Microservice modernization optimizes CPU and memory properly, so during peak times the financial team's month-end processing will not experience issues. Multi-tenant and cross-department isolation allow an admin to segment the environment logically, enabling teams to manage their own localized workload and permissions within a unified platform without degrading global performance.

Control-M's scalability varies in both horizontal and vertical directions effectively. It is engineered for large enterprises and can scale workload for millions in a day while ensuring new platforms are added seamlessly.

A classic scenario for Control-M scalability is during financial close of the month or quarter. In high-pressure scenarios, processes must scale from normal operations to running more than 50,000 or about a million jobs, with each process needing to be properly followed. Control-M agents deployed on clusters can be easily leveraged while flexing the environment, with Kubernetes pods working properly to absorb heavily computational load. Prioritization and throttling prevent resource crashes when resources are exhausted. The distributed architecture allows the operation team to dynamically adjust the resource pool, providing more data for the financial compliance team when they need more requirements with time-sensitive backgrounds.

The central servers coordinate while distributed agents handle heavy lifting in execution, preventing bottlenecks. During massive searches in real-time on a dashboard, depending on the task, the cache can be cleared at any time and run anonymously. Without this level of horizontal scaling, a search would typically cause a job queue, but Control-M enables the IT and ops team to operate effectively.

Control-M has a global support center that operates under the follow-the-sun rule with 24/7 coverage. They offer an escalation pathway for faster resolution. For premium support, 24/7 assistance is available, though standard support has more limited coverage.

Control-M maintains extensive technical resources with a proper document library and community forum. Control-M has matured into a long-standing enterprise platform with many repositories for troubleshooting and guides. Self-service support resolves issues with REST API and others effectively, suggesting appropriate outputs. Escalation support is available as we purchased Control-M directly from BMC, which provides additional leverage. When issues become bottlenecks to resolve, faster response times and more effective diagnosis of complex issues are possible.

Overall, the customer support is robust and excellent for a Tier 1 enterprise vendor. I would rate Control-M's customer support at eight out of ten. The reason for this rating is that they provide extensive documentation for everything, maintain proper rules to follow, and offer strong support during emergency situations.

For anyone considering Control-M, I would definitely recommend embracing Jobs-as-Code. For small enterprises, I would recommend starting with Control-M even though it may be costly initially, as it will help significantly in the long run. Control-M supports GitOps integration along with JSON and YAML, making it much better long-term. I would strictly recommend implementing it from day one to have all access available from the start and plan costs accordingly. Although it is costly initially, it pays off quite well in the long run by saving the association resources. I would also recommend going with hybrid boundaries to implement it properly.

We use Control-M for running scripts, database control, and other development purposes.

We run queries related to product PLP and PDP, and for other tasks, such as payloads, we write queries in Control-M to fetch and maintain them.

With Control-M, without human effort, it automatically runs queries, fetches databases and scripts, and runs other work as well, such as pipelines.

Using Control-M has made us faster and more efficient in our productivity.

By using Control-M, we handle more tasks without taking more than five to six hours to debug and fix errors. We reduced that time to at least two to three hours, completing the task within two hours. Running a pipeline also used to take more time, causing issues, but after using Control-M, that pipeline runs smoothly within 30 minutes, which also reduces human effort.

Control-M offers features such as running queries, maintaining a database, running a pipeline, and some AI assistance, providing more features now that reduce human effort in the IT industry.

AI assistance means that in daily tasks, without AI assistance, a human can take more hours of effort to complete tasks. For debugging and development purposes, we are using AI with the help of Control-M.

Control-M can improve by adding more reliable features, such as extensions for other AI models that will enhance it.

The UI can be integrated much more easily to be human-readable, so a developer can read it easily, which will help.

There are no improvements needed for Control-M that I haven't mentioned yet. It's pretty cool.

We have been using Control-M for around two-plus years.

On a scale of 1 to 10, I rate Control-M overall a nine.

I chose nine out of 10 because it makes the lives of developers and other fellow software engineers easier.

Governance and security are good, and after using Control-M, it is more secure compared to others.

Accuracy is very high, and reliability is very high with Control-M's AI capabilities.

I will definitely advise my fellow friends and colleagues to use Control-M more.

My main use case for Control-M is job scheduling. As a specific example of how I use Control-M for job scheduling, we schedule daily jobs of the banking sectors for their transaction processing.

Managing the integration and sequencing of data processing across diverse platforms is somewhat challenging, but we maintain integrations from various data platforms to ensure a controlled process. We have our own AI ops strategy to help with this.

We are planning to use Control-M to support AI or ML workloads because AI will eliminate the manual effort currently involved in batch operations, thereby providing efficiencies.

Control-M has facilitated the integration of Kubernetes or cloud-native workflows with traditional batch processing. We faced difficulties with multiple applications in containerized platforms, but we overcame them with the support teams in our organization who had good knowledge.

For compliance requirements like SOX and audit trails, we have a different tool called Apexa to help with vulnerabilities, but we currently use Control-M solely for batch processing.

Control-M has positively impacted my organization by helping us manage jobs in a timely manner and contributing to customer success.

In terms of specific outcomes or metrics from using Control-M, it was basically about the time saved. If we had to normally run the jobs with manual effort, it used to take time, but scheduling has helped us save a lot. The output accuracy has also improved, helping our teams deliver jobs on time, which has increased customer satisfaction.

The best features Control-M offers are the scheduling features, and if there are any failures, it helps in troubleshooting and fixing it as well.

Control-M helps with troubleshooting and fixing failures by allowing us to check the results and track the logs whenever there are failures, which helps us to give the exact failure information so that we can proceed to get them fixed.

Regarding Control-M's AI capabilities, governance is always there. On the governance front, it is helping us provide a human-in-loop for validations and approvals on the process of actions, which helps us manage in a coordinated way.

The accuracy and reliability of Control-M's output is nearly 99%, which is excellent for the jobs we perform, providing us with the required output.

Control-M can be improved in the area of auto-remediation, where we are looking for improvements that can help eliminate the need for operations teams.

I have been using Control-M for almost four years.

Control-M is stable.

Control-M's scalability is beneficial since it is available for cloud service providers, allowing us to apply across various service providers with whom customers are onboarded.

Customer support for Control-M is very good. Users are satisfied because the tool delivers the required output, with jobs running and scheduled on time.

Previously, we used a script-based method for normal batch processing, and we switched to Control-M because it proved to be more efficient and provided the required outputs.

We have experienced a return on investment with Control-M, reducing from almost 10 FTEs managing job processing and failures down to four FTEs after its introduction, yielding significant efficiencies.

My experience with the pricing, setup cost, and licensing of Control-M aligns with market standards, and I find the product to be reliable for our needs in getting the required jobs done.

Before choosing Control-M, we evaluated other options available in the market which we found to be not useful.

I would rate Control-M a nine on a scale of one to ten. I gave it a nine because the tool has become so sophisticated and improved a lot since we started using it, and now it meets our requirements, which has helped improve our customer scores. I suggest others consider trying Control-M over other tools like Autosys since it provides a strong return on value.

Like any other batch scheduler, Control-M is what we're really using for the various workflows that we have to either do on a daily or hourly or whatever basis. We run them all through there.

I've worked with other ones, and I think the certain simplicity to how Control-M lets you set up a schedule or workflow is excellent. It's very easy to build everything together.

Most of my complaints have ever been with support for Control-M, not with the product itself. I can't really think of anything that I strongly dislike about the product.

Sometimes my gripes with the support relate to them being a little slow to get back on either a query or a problem issue. That's my biggest gripe on the support side. There are some people in the support area that are fantastic, and then there are others that feel like I'm being pushed off to the side. I don't know what's going on in the back shop, so I can't say for certain.

I'm currently fighting with support on one issue right now with Control-M, but it's not the overall product, it's just one sub-piece that's being problematic. It's the SAP interface with Control-M.

My usage has definitely been more than ten years. I go back to release three or something.

I've never really seen much of a problem with scalability for Control-M. I'm sure there is an upper limit to how many agents and how many jobs you could run, but I haven't hit that yet. Where I am right now, we load probably about three thousand jobs a day, but we run a lot more than that because you can load a job and run it hundreds of times.

I'm going to give Control-M's support an eight on the scale from one to ten, with ten being the highest. That rating is mostly because of the reasons I've already mentioned.

I've used plenty of alternatives for Control-M in the past. Though some of them don't exist anymore or they probably still do. One of my former employers was a big CA-7 shop on the mainframe side, and on the distributed side, I used the IBM tool Workload Scheduler.

The setup for Control-M is not horrible. Once you get the server built out correctly initially, it installs relatively easily. There are some things in the update format that I don't favor. They used to have an update and migrate model, which would allow you to move from one system to a new system if you needed to upgrade your operating system or switch to a different platform. Going from Windows to Linux, or from SUSE Linux to RHEL Linux was easy to do. That migrate model was very good, but they went to an upgrade in place model. You can't do it that easily anymore because what you have to do is upgrade in place where you are and then build a new box and then move the data over, which is a bit of a pain. It was one-stop shopping previously. They stopped that at version 9.18.

The implementation is handled by me and maybe one other person who are specifically doing the deployment and maintenance of Control-M.

I don't really have any thoughts about the pricing for Control-M. I don't deal with that, or I haven't in a very long time. I know one of the pricing models is based on workload, specifically how many tasks you load in a day. I don't know if there are any other pricing models other than that. That's the only one I'm familiar with.

Control-M does require some maintenance on your end, as with any software. There are fix packs released or patches, and you need to be aware of that. BMC is very good about notifying you when they post out new patches or fix packs. It usually requires a downtime, but it's a very short downtime. It takes longer to take the product down than to apply the patch for Control-M. You have all the processes to shut down, apply the patch, and bring them all back up, and the up and down takes longer than the actual patch application sometimes. I would rate this review a nine out of ten.

I have been working with Control-M for about six months as part of my role. During this time, I have mainly used it for monitoring and managing batch jobs and automated workflows.

Our main use case for Control-M is managing and monitoring batch workflows across different systems. We use it to schedule jobs that run scripts, database processes, and ETL-related tasks. We make sure they execute in the correct order based on dependencies. On a daily basis, I mostly work with monitoring job runs, checking job statuses, and troubleshooting failures when a job does not complete successfully. We also review logs, rerun jobs when needed, and make sure the workflows complete within the expected time windows. Control-M helps centralize all this so we can track and manage automation more efficiently instead of handling tasks manually.

One of the examples for centralized monitoring in Control-M is the ability to view the status of all the scheduled jobs from a single dashboard. Instead of checking multiple systems individually, we can see whether jobs are running, completed successfully, or failed in one place. For example, if a job that runs a database script fails during the night schedule, we can quickly identify the failure from the monitoring interface, review the logs, and rerun the job if needed. This helps the team respond faster and keep the workflow running smoothly.

One of the best features of Control-M is its ability to manage complex job scheduling and dependencies across different systems from a single platform. It makes it much easier to automate workflows and monitor job execution in real-time. The centralized monitoring and alerting help us quickly identify failures and take action, which improves reliability and reduces manual effort.

Control-M has had a positive impact by improving the automation and reliability in our batch processing workflows. It helps ensure that jobs run in the correct sequence and reduces the need for manual intervention. The monitoring and alerting features have also made it easier to detect failures early and resolve issues quickly, so it helps keep our scheduled processes running smoothly.

One area that could be improved is the user interface. While the platform is very powerful, the UI can sometimes feel complex for new users, and it may take time to become familiar with all the features. Improving it and making the navigation more intuitive would help teams adopt it more quickly.

Another improvement could be simplifying the initial setup configuration process for organizations that are implementing Control-M for the first time.

I have been employed for almost four years, approximately three years and ten months.

Control-M is definitely stable. In my experience, once workflows and jobs are properly configured, it runs reliably and handles scheduled processes consistently. Most issues we encountered are usually related to the jobs themselves rather than the platform, and the monitoring tool helps identify and resolve them quickly.

Control-M is quite scalable in my experience. It can handle a large number of jobs and workflows across different systems without major performance issues. As the workload grows, it is possible to expand the environment and manage additional processes while still maintaining centralized monitoring and control.

Customer support has generally been good. The support team is responsive and provides helpful guidance when issues arise. The documentation and knowledge base resources are also useful for troubleshooting common problems.

Before using Control-M, some workflows were handled through basic scheduling tools and manual scripts. Moving to Control-M helped centralize job scheduling and monitoring, making it easier to manage dependencies and automate processes more reliably.

The biggest lesson I learned while working with Control-M is the importance of properly defining job dependencies and workflows during the initial setup. When dependencies are clearly configured, the automation runs smoothly and requires less manual intervention. It has also highlighted how valuable centralized monitoring is because it allows teams to quickly identify and resolve issues before they impact downstream processes.

We are just a user.

For return on investment, we have experienced improved automation and reduced manual effort. In terms of operational efficiency, automation through Control-M has reduced manual overhead by around twenty to thirty percent, especially for routine batch job monitoring and scheduled tasks.

I have no idea how the pricing, setup, and cost licensing is done. It is done by the finance department.

We saw the working methodology of Control-M, how batch jobs are handled, and how the automation works, so we just went for Control-M.

With job scheduling and workflow automation, this automation has increased the scheduling time by fifty percent. The monitoring task has been reduced by twenty to thirty percent. Instead of going on multiple tabs, we can view it at once. Workflow management through the technologies is a bit of a complex task. As we have used this, we can implement it. For new users, it might be a bit complex.

Currently, we have been using this for the past six months. We are seeing good, positive results. The automation workflow is also good, and the batch scheduling jobs are definitely good. We will still want to try it on different platforms and then decide on any further usage or increase in usage of Control-M.

In production, this workflow is mainly through the monitoring and reporting features in Control-M. We check the job status to make sure the scheduled process completes successfully within the expected time window. If the job fails or is delayed, we review the logs again, analyze the dependency chain, and rerun or troubleshoot the job if needed. This helps ensure that the overall production workflow continues without impacting downstream processes.

One piece of advice I would give is to spend time planning the job dependencies and workflows carefully during the initial stages. If the workflow is well-structured, Control-M can automate processes very efficiently and reduce manual intervention repeatedly.

Overall, Control-M has been a reliable solution for managing automated workflows and scheduled jobs. It provides good visibility into job execution and helps teams maintain operational stability. I gave Control-M a rating of eight because it is a very reliable solution for scheduling jobs and automating workflows, and it helps me manage complex job dependencies and provides good monitoring capabilities, which makes it easier to track and troubleshoot batch processing. The reason I did not rate it higher is that the interface can feel complex for new users, and the initial setup and learning curve could be improved. With some improvements to the user interface and onboarding experience for new users, it could become even more effective.

Control-M is used for scheduling, specifically scheduling application jobs. We have always been using Control-M, as we inherited it. We work with all technologies within the business using Control-M, including WebMethods, Axway, and IBM MQ. In the managed file transfer space, using Control-M, I find that it is not as user-friendly as other products available for MFT.

The best features in Control-M are its ease of use and robustness; it is very feature-rich, which is what we use it for—scheduling. It is easy to integrate Control-M with technologies for our DataOps and DevOps processes as things change. The integration aspects of Control-M are out of the box, so they are straightforward to use. From using Control-M, I have seen improvements as they grow with the versions; with the newer versions come enhanced functionalities, such as the latest version allowing access through a web GUI instead of the client GUI that you have to install, which is quite helpful because you can access it from anywhere.

We are not on the latest version of Control-M; we currently have version 20 and 21.

I have been using Control-M for 10 years.

Regarding stability with Control-M, I would rate it nine out of ten for downtime, bugs, and glitches.

Control-M is very scalable, and I would rate it a nine.

I would rate the vendor's technical support for Control-M as a nine.

Positive

We have tried to look at other products, but there is no other product out there that does what it needs to do as Control-M does, which is why it is still around—it simply does what it needs to do.

The deployment of Control-M was quite complex to get in, but once it is in, it does what it needs to do. It took weeks to get Control-M deployed.

Control-M requires maintenance from our end, as we have to perform patching whenever needed, but that does not happen very often—probably once a quarter. Patching for Control-M is easy.

I have definitely seen a return on investment with Control-M in terms of time and resources, but I cannot speak to the financial aspect—I do not know. I would estimate that I have saved perhaps 20% to 30% on time and resources using Control-M.

From what I know about pricing, I would probably put Control-M in the expensive category, but you do pay for what you get; you are paying for a premium product.

We looked at AWS products for scheduling with Control-M; I cannot remember the actual name of the scheduling tool at AWS, but it is nowhere near as advanced as what we need.

Approximately 100 users work with Control-M. They are not all Australia-based; some users are from India, so we have offshore resources as well. My relationship with BMC is both transformative and transactional. Regarding the transformative aspect, I have impressions of BMC as both because we partner with them; we might not be strategic partners, but we value their advice all the time—not just product advice, but sales as well. We consider ourselves a partner with the vendor, but I do not know if we are officially a signed partner; we are a partner at the base level. When I refer to our relationship with the vendor, we are considered an entry level partner; we are not a reseller, so we cannot resell their products, but we are partners and we consult while using their products internally and with customers to support their customer base. Our clients are generally enterprise businesses. I would recommend Control-M to other users; I know they are going all web-based, which they believe is the best way to go, but I can tell you that everybody I have spoken to has said the contrary—they actually prefer the client GUI that you can install, which is easier to use and more feature-rich, while the web GUI is very hard and difficult to navigate through. I have rated this review a nine out of ten overall.

My main use case for Control-M is building a data platform that brings data from multiple sources from disparate systems. I use Control-M as a data orchestration tool for data monitoring and scheduling jobs for observability purposes, with a focus on AI-powered data observability and job monitoring.

I manage the integration and sequencing of data processing across diverse data platforms and cloud environments by setting up the predecessors and successors in the workflows.

My organization is already using Control-M to support AI acceleration by bringing data from disparate sources into our data platform. Control-M has facilitated the integration of Kubernetes and cloud-native workflows with traditional batch processing by utilizing DevOps for CI/CD, which is effective during deployment and production migration.

For compliance requirements such as SOX and audit trails, I implement role-based access control as part of our data governance with Control-M.

Control-M has positively impacted my organization as it stands out as one of the best tools compared to competitors in the market, particularly in terms of cost-effectiveness, reliability, and ease of maintenance, along with a user-friendly interface.

I have noticed significant time saved, particularly with mean time to rectify issues since using Control-M.

The best features Control-M offers for me are an easy way of scheduling jobs and monitoring, setting up predecessors and successors, and providing good control to the user who is monitoring for the data engineer.

Out of those features, I rely most on setting up predecessors and successors and maintaining the graph of which job has failed and how to rectify it as the most significant aspect of my workflow.

The observability features are very good, especially the job monitoring feature.

Control-M can be improved by enhancing data flow monitoring capabilities and addressing some data engineering needs.

I would also like to see improvements in user experience via mobile and support for iOS and Android with a nice UI interface.

Regarding Control-M's AI capabilities, I think implementing a role-based access mechanism for governance and security would be perfect.

One improvement I need is to introduce an AI-powered agent, which would make Control-M unique compared to others in the digital world.

I have been using Control-M for around seven years.

Control-M is stable.

Control-M's scalability is very good; adding nodes and servers is easy on the fly.

Customer support for Control-M is excellent. If I face any issues, I can easily reach the support team and get resolutions within the defined timelines set at the initial purchasing time. I would rate customer support a nine, definitely.

Prior to Control-M, I used a different solution, AWS Workflows.

I have seen a huge return on investment with significant time savings by investing in AI-powered solutions and integrating with the cloud.

My experience with Control-M's pricing, setup cost, and licensing has been positive, as I find it a good product with excellent features that add value for customers, and the cost is reasonable compared to others.

Before choosing Control-M, I evaluated options such as Ansys and cron.

On a scale of one to ten, I would definitely give Control-M a ten because it is a very good tool from BMC. I rate it a ten because it is such a reliable data pipeline monitoring tool that I have seen in the market. The quality of data, particularly in setting up predecessor and successor jobs in the pipelines, makes a significant difference in any data pipeline's success. My advice for others looking into using Control-M is that it is one of the best reliable products in the market for on-premise, private cloud, and public cloud deployments.

My main use case for Control-M is the Control-M infrastructure. In my day-to-day work, I use the web and GUI console for Control-M infrastructure. With the web and GUI console in Control-M, I manage processes such as scheduling, monitoring jobs, and handling upgrade migrations. I handle tasks with Control-M including upgrades, disaster recovery, testing jobs, and scheduling jobs.

I manage the integration and sequencing of data processing across diverse data platforms and cloud environments using Control-M Enterprise Management. My organization is currently planning to use Control-M to support AI or ML workloads, and we are willing to implement AI with ML workloads.

Regarding Control-M facilitating the integration of Kubernetes or cloud-native workflows with traditional batch processing, I do not see any difficulties while configuring. We will be using AI, but we have not reached that point yet, although we are willing to do so. I use Control-M to address compliance requirements such as SOX, ensuring that we meet audit trails and regulatory reporting.

Control-M has positively impacted my organization with significant improvements. We have many customers and perform production work, with numerous services being utilized by customers. Specific improvements noted since using Control-M include our ability to perform extensive automation, especially with scripts across the organization, as well as numerous agent installations and software installations that we manage with Control-M.

The best features that Control-M offers are Data Assurance and MFT. Data Assurance and MFT stand out to me in Control-M because we manage files for transfer and ensure Data Assurance. Besides those features, we also handle agent installations, agent automation, and remote agents for data grouping in Control-M.

I am satisfied with Control-M's governance and security capabilities. In terms of Control-M's AI capabilities, I believe its accuracy and reliability of output depend on the inputs and data values, which allows us to rely on that output.

I believe Control-M could be improved in customer support and vendor support, as we desire improvements there, as well as advancements in Agentic AI and upgrades to newer versions of Control-M that support multiple web fixes. Customer support should offer better immediate solutions whenever we contact them about an issue.

I rate Control-M nine out of ten because I believe customer support and vendor support require improvement, making the user experience less interactive.

I have been using Control-M for five years.

Control-M is stable.

Regarding Control-M's scalability, we have scalability based on the license, allowing us to scale up.

We have great customer support with Control-M.

I previously used Autosys before switching to Control-M.

We have seen a return on investment. There is money saved, and we have reduced the amount of manual jobs, allowing Control-M to save us significant resources, especially on human intervention.

I am very satisfied with the pricing and the cost of licensing for Control-M.

Before choosing Control-M, I evaluated CA-UWS among other options.

I rate Control-M a nine on a scale of one to ten. In my organization, we deploy Control-M using a combination of private cloud as well as hybrid cloud. For our private and hybrid cloud deployments, we use IBM as well as Azure as our cloud providers. My advice to others looking into using Control-M is that it is one of the best tools available in the market today, enabling you to perform extensive automation and workload orchestration.

My main use case for Control-M is to schedule jobs to run particular things, to load files from one path to another path, which I do daily. To load some data into the cloud, I utilize particular jobs inside Control-M, where I usually create the jobs and monitor their execution.

A quick example of a job I schedule or monitor in Control-M is defining a job name, job details, weekly schedule, monthly schedule, and daily schedule, according to which I schedule the jobs.

In my day-to-day operation role, Control-M is mainly used to monitor, manage, and troubleshoot bad jobs. For example, for monitoring job execution, I check running jobs in the monitoring domain and verify if the job's completed status is ended okay or if any failures occurred. If it is executing for a long time, I can mark it as long-running.

Analysis of the job failure involves opening a job output or logs to analyze the failure within Control-M and checking for application errors, script errors, database issues, or file-level issues to coordinate with the application team if needed. These are the aspects I usually analyze when job failures occur. When rerunning a job, I check and find the issue; if I find the issue in the Control-M logs, that is fine. If I cannot find any issue, I log into the server and check the application logs, then debug and rerun the job. I also monitor the SLAs.

Currently, I am not using Control-M to support AI or ML workloads; I primarily use it for batch monitoring and loading data to customers.

I do not utilize Control-M much for compliance requirements; I mainly use the production environment for loading and monitoring jobs only.

Control-M positively impacts my organization by automatically handling batch processing, reducing manual efforts, improving reliability, and ensuring critical business workflows are completed on time. It provides centralized monitoring, automated scheduling, dependency management, and proactive alerting for missing elements and also generates reports.

For example, the File Watcher prevents jobs from failing due to input file delays, leading to better SLA compliance for critical batches like claims, payrolls, or reporting processes. The visibility provided by a single dashboard allows for end-to-end monitoring of jobs and workflows. Resource automation through reduced manual scheduling and monitoring lets teams focus on higher value activities.

In my environment, Control-M helps monitor daily batch streams, identify failures early, track downstream impacts, rerun jobs after resolving issues, and ensure successful completion of business-critical processes, reducing downtime and improving service reliability for business users.

The best features Control-M offers include centralized job scheduling, allowing me to schedule any kind of jobs based on Windows, Linux, Unix, database, Informatica, Hadoop, and cloud applications without needing to log into multiple servers. Additionally, Control-M automatically manages job dependencies, such as extracting data, transferring data, loading data, and report generation, while also providing real-time monitoring for operations to use for running jobs and quick identification of production issues.

Automatic alerts and notifications are set for job failures, missing files, SLA risks, or long-running jobs, and I can trigger these alerts inside Control-M and send notifications via email, ServiceNow, Teams, or other platforms. The tool also allows easy recovery and reruns of jobs, including holding, freeing, or post okay, and ordering jobs if needed. Moreover, features like File Watchers help avoid job failures due to missing files, and calendar-based scheduling allows me to set times for jobs daily, weekly, or monthly. Cross-application workflows like MoveIT file transfer, Unix scripts, and email notifications are integrated. Finally, auditing and reporting capabilities manage execution history, user actions, job logs, and compliance records.

The File Watchers are really valuable features in Control-M that I find helpful. For instance, I had dependencies for files where I need to get the raw data from them, and once the file is present in the specific path, the job executes. However, if the file is missing at the scheduled time, the job fails. This is particularly problematic since delays can impact production. The File Watcher helps prevent job failure due to files missing, especially when delays happen, such as vendor delays or issues in file transfers. It significantly reduces manual monitoring and improves SLA compliance by ensuring jobs start immediately after the file is received. If the file is missing throughout the scheduling day, an alert is generated.

The integration across different platforms and cloud environments is performing very well, and I never receive complaints regarding this aspect.

Control-M is a powerful workload automation tool, but there are areas for enhancement. The user interface can be more intuitive and interactive, particularly for new operators. Implementing AI-driven predictive analysis cloud capabilities could help in predicting job failures before they occur. Enhanced cloud-native integrations and more dedicated root cause analysis dashboards would further improve the operational effort and incident response time.

Control-M job documentation, audit logs, and everything related are currently satisfactory; I do not see necessary improvements here. However, I could integrate more tools and introduce AI agents in Control-M to assist new users in understanding better and guiding them in creating jobs or monitoring actions.

I have been using Control-M for the last three and a half years.

On a scale of one to ten, I can rate Control-M around an eight because it is a powerful tool that I have previously used.

I would rate Control-M an eight out of ten. It is excellent for workload automation, dependencies, SLAs, and everything in between. I did not give it a nine because troubleshooting complex workloads sometimes requires specialized knowledge, and the interface can feel less interactive for new users. Moreover, there is still a dependency on the underlying application and interface; for instance, if a database, network, or application issue occurs, Control-M can detect and report the failure but cannot always resolve the root cause automatically. Overall, it is a strong enterprise scheduler but has room for usability and self-handling improvements.

Regarding Control-M's AI capabilities, I believe the value comes from faster operations, but governance and security must remain top priorities in enterprise environments such as banking, healthcare, insurance, and retail. From a governance perspective, Control-M should offer recommendations rather than autonomous actions on critical production workflows while maintaining an audit trail that tracks changes, reruns, and approvals. On the security side, important measures include ensuring AI only accesses job metadata and log scheduling, without gaining access to customer data or sensitive information.

The accuracy and reliability of Control-M's AI output meet my expectations. I find its performance very reliable, and I appreciate the AI features, although there is still room for improvement in certain areas.

I definitely advise others to consider using Control-M because of its simplicity and cleanliness.