Control-M Reviews

Control-M manages pretty much everything in our hemisphere, helping us meet our financial regulatory obligations, file transfers, running scripts, PowerShell, and SQL, making it critical to our day-to-day operations.

Control-M supports our DataOps and DevOps initiatives by providing an avenue for our DevOps teams to problem-solve in an easy way, giving them a platform to build on rather than having to start from scratch.

The measurable benefits or improvements we've achieved with Control-M are critical in the finance industry, as it keeps us on target with all regulatory requirements. Without Control-M, I don't know where we'd be, and if we shut it off, the business would probably run for about six hours before we faced serious issues, highlighting its role as a key component to our success.

Control-M has definitely enabled new capabilities and business processes that weren't possible before, allowing us to go to other departments and problem-solve for them, eliminating manual tasks that have been done for years. Departments now benefit from not even needing to look back at whether a task is being done since the information is readily available, providing them more time in their day for productivity and enhancing life for our customers.

Control-M is a great product already, but everything can do with a bit of improvement. Personally, I'd like to see a little bit more color in the web interface, and in terms of its technical ability, the one thing I would be critical about is a bit more user-friendliness with the reports and the way we input information into it.

I've been working with Control-M for three years.

Once we have tested things and gotten them into play, during the three years that I've been working with Control-M, I've encountered only one problem, and BMC's support has been quite good, allowing us to solve that issue quickly and easily.

Once we have tested things and gotten them into play, during the three years that I've been working with Control-M, I've encountered only one problem, and BMC's support has been quite good, allowing us to solve that issue quickly and easily.

The biggest return on investment from using Control-M, from my point of view, is the ease of use and the time it gives our employees back in their day to be more productive.

I would give Control-M a very good rating in building, scheduling, managing, and monitoring workflows. It is pretty easy to use, and we have taken people without any type of formal training and been able to get them into using Control-M fully as a scheduler within weeks, proving its ease of use. In terms of its use for scheduling and building, it provides options, and it comes back to having flexibility, which is appreciated by anyone who has worked in the build area. With all the plug-in options and various job types that you can create, it increases the flexibility and the avenues available for using Control-M as a solution.

I've not had much interaction with licensing. In terms of costs, I think in life you have to pay for what you want, and generally, if you want quality, you've got to pay for it, but in my limited knowledge of pricing outside of Control-M and BMC, I think it is competitive, recognizing there's not a lot out there like Control-M, making it difficult to determine what the price should be as it is a critical piece of work worth its value. I would rate this product an 8.5 out of 10.

On-premises

I have been using Control-M on a daily basis. My main use case for Control-M is the scheduling of processing of jobs. A specific example of a job I schedule with Control-M is OS jobs that run a script for backup.

I use Control-M day-to-day mainly for database jobs, OS jobs, MFT jobs, file transfer jobs, and many more.

In my opinion, the best features Control-M offers are advanced scheduling and the processing of various processes at a scheduled time.

Control-M has impacted my organization positively by automating many of our daily based tasks. The automation has helped us as taking backup has become really easy; earlier, we used to do it manually, but now with the help of Control-M, we do it through automation.

Control-M is deployed in my organization on-premises. It is easy to integrate Control-M with other technologies. We have added AWS cloud as of now, and we are trying to move all of the infrastructure jobs to the cloud.

Control-M has improved the way my organization functions by mainly automating all the backups and database jobs that we used to do manually. The implementation of Control-M has had a great impact on business-critical applications as it provides clear monitoring and troubleshooting for business-critical jobs within the SLA.

Everything is good regarding improvements for Control-M. There is no need for additional improvements.

I have been working in my current field for seven months.

Control-M is stable.

Control-M's scalability is great.

The customer support is good. My experience with Control-M's customer support was good, and I would say it was helpful and responsive.

I previously used Autosys. Before using Control-M, my organization used Stonebranch because it was what we relied on for job scheduling and automation. I switched from Stonebranch to Control-M because it was hard to understand, the scheduling was difficult, and it had fewer integration options with technologies.

We directly chose Control-M without evaluating other options.

I have seen a return on investment with Control-M as we need fewer employees because it is really automated.

I think the forecast is a feature to consider. I assess Control-M for building, scheduling, managing, and monitoring production workflows primarily through the Control-M GUI. The accuracy and reliability of Control-M's AI output are ninety percent accurate and reliable. My advice to others looking into using Control-M is to have it in their organization. I find this interview good and do not think any changes are needed for the future. I would rate Control-M a ten out of ten.

My use case for Control-M is that it's a job scheduler for some jobs regarding data warehouse jobs and billing tasks for a telecommunication company, mainly monitoring jobs.

The best features of Control-M that I most appreciate are the integration and unification of different systems, such as BMC Remedy, integration with alerting systems, and the unification for the dashboard—something akin to one dashboard to monitor everything, which is very good. It can communicate with different platforms such as cloud, different systems, and OSes. I also appreciate the visualization; when we are designing a tree, a job tree, the option to visualize the dependencies and the mapping is very user-friendly.

Control-M has positively impacted my organization, particularly in the flexibility it offers in scheduling jobs. It has a nice feature called Calendar Integration that integrates with the company calendar to allow for the holidays and special events regarding the organization, not only the public calendar, but specifically for the organization.

There are some areas in Control-M that have room for improvement, particularly some constraints regarding the scripts, such as limitations in how they can be executed and integrated; it's not the normal scripting way in some cases. It's not in all cases, but in some cases, there are limitations and constraints in running the scripts. 

Additionally, Control-M requires some hardware resources in terms of system requirements; it consumes some hardware resources.

I have been using Control-M for about five years or more than five years.

The stability of Control-M gets a nine from me; although we faced one issue during this year regarding its stability, nine is good for it.

Scalability for Control-M is good; I would rate it an eight due to the high license cost, but it's scalable.

I would rate the technical support for Control-M a nine.

Positive

I have seen a return on investment with Control-M; we have the real-time alert feature. Our administrators get alerts for any job failures or emails for any issues, which saves our business. We also have reporting tools embedded in Control-M to generate daily reports and keep historical data. All of this handles our job, mainly the monitoring and automation for the scheduling. That's why we are using it.

My thoughts on the pricing of Control-M are that the cost of the license is very high. You have to implement some cost-saving measures, such as cleaning up jobs that are not required anymore on a monthly basis, in order to control the license, as the license is very costly. 

Additionally, there's a dependency on training; on a yearly basis, or whenever there's a new version, we need to schedule training and an official training from an accredited course center or from BMC itself, which is very costly.

I haven't dealt with other solutions or vendors on the market, but I can say Control-M is better than good when it comes to automation.

There is a good feature about the drag-and-drop; we can easily create and modify jobs with drag-and-drop in the interface, which makes it easier and user-friendly. BMC is a good strategic partner; they are helping us in mapping out our migration strategy, and we have a team from their side that supports us in our job. They know our case and they are specialized in our system, following up on our system.

I recommend Control-M to other users because it's user-friendly, it has a unified dashboard, and it's easy to schedule and use. However, there are certain limitations, especially for larger organizations, to afford the cost of the license and the cost of training. For a small organization, I wouldn't recommend it, as it would be very costly for them.

I would rate Control-M an eight out of ten, considering I have some concerns about the cost and the training, which is also related to cost. 

Hybrid Cloud

It is a job scheduler. It is used for scheduling jobs.

It is useful for any sequence of jobs that are complicated, such as Job A can't run after Job B, but if Job C hasn't run, you can't run Job B. Building that logic into a script is almost impossible. Control-M solves that problem. Normally, in large banks, there are many different dependencies. It helps with dependency mapping.

Banks need to bring the branches online at seven o'clock in the morning, so you have to finish your batch processing by the time you bring the branches online. Typically, if you've got a big outage in the middle of the night, it would take hours to fix, which means you will run late, and your backups and all other jobs will not be completed by the time your branches open their doors. Control-M can manage that for you. It can make some smart predictions and change the workflow dynamically so that businesses can run with predictability every night.

It keeps the run times of all jobs. If you need an SLA to complete a particular suite of jobs by a particular time, for example, 2 AM, it can provide the historical average run times of each job. It can help predict or forward plan to see what time it's going to finish those particular jobs. It can do predictive analysis, so if it's not going to finish by 2 AM, it can warn you that it's not going to finish by 2 AM. You can then build in some actions. Some of them may be less important. You can omit those for the night to save time.

A large bank in South Africa would have more than one million jobs to be run each and every night. If something goes wrong in the middle of a million jobs, it can be very complicated if you're managing that via scripts or manually. Control-M solves that problem.

It has a graphic representation of the job flow. It has a very nice GUI to help you understand the sequence of events. On the GUI, if a job is green, it's running or it's completed. If a job is red, there's a problem. It uses alerting and color coding to assist the operator.

Control-M is the number one leading product in the world. What they've done about scheduling, other people are still trying to figure out, so it's difficult for me to propose anything new. There is not so much AI at this point in time, but I guess it's coming. However, predictive analysis is built into it.

I have been using this solution for 20 years.

There are no complaints regarding stability.

There are no complaints regarding scalability. I sell it to most of the large enterprises, but it's also applicable to medium enterprises.

They are very good because this is a tool that requires 24/7 support. If something fails at 3 AM in the morning, you need to fix it and get it back up and working really quickly. You can't afford to have the tool down for long.

Positive

It is very simple as long as you know the prerequisites. 

It's worth the money. It is cost-effective because you need fewer things. It has a high level of automation. Staff can go home at five o'clock. You can run a million batch jobs or tasks at night when all of your highly skilled people are at home sleeping. When your staff comes in the next morning, all of that work is completed, and the business is ready for the next day

It depends. It's packaged in such a way that you can buy the base model without all of the fancy stuff. You can try and keep your price similar to competitors. I guess it's natural throughout the world. It doesn't matter whether you're buying cell phones or something else. The best cell phone will always be more expensive.

There are other solutions, but the difference is that Control-M has constantly undergone development. Each and every year, many improvements have been coming out. The GUI is one example. Often, people think about job scheduling as something you did in the 1970s or 1980s. You don't do that anymore. A lot of the competitor tools are legacy. They're kind of locked in. That's how they work. They're not trying to evolve. We used to talk about job scheduling many years ago, but now, it is orchestration. There are fewer tools that can do proper orchestration.

The fact that it has been in the top right-hand quadrant for 20 years tells you everything about the tool.

I would rate Control-M a nine out of ten. I have been a reseller of the tool for 20 years. I wouldn't be doing it if I didn't believe in the tool, and I didn't like it a lot. I am proud to say almost all of the banks in South Africa are using it. That speaks for itself.

My main use case for Control-M is using it for financing ratio jobs, schedulers, and related tasks.

A specific example of how Control-M helps me with this in my daily operations is that we have data in multiple places scattered in different formats, so I write Control-M jobs to collect all the results and derive insights from it.

Control-M fits into my workflow by helping us trigger workflows.

Control-M is used to run the daily jobs across our different business hours.

Control-M allows me to manage the integration and sequencing of data processing across diverse data platforms and cloud environments.

Control-M has positively impacted my organization, and I have noticed improvements and benefits since using it.

Those improvements include significant time savings, as one single person can orchestrate multiple jobs irrespective of the platform or technology stack. Additionally, Control-M has reduced errors in our operations.

The best features Control-M offers are security, orchestration engine, and its job states such as successful or failed.

What makes the security feature stand out is that we are working in the BFSI domain, where we have very high compliance requirements.

Compliance is the major consideration I must maintain regarding Control-M features.

Regarding Control-M's governance capabilities, it allows me to check at what time a job is running.

This works by helping me monitor sensitive information at certain checkpoints and ensure compliance at specific points.

Control-M can be improved with stronger AI capabilities, as it is architecturally weak in this area. I need to troubleshoot failure jobs more efficiently.

I would like to see more improvements specifically regarding AI troubleshooting capability.

I have been using Control-M for ten years.

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

Regarding Control-M's AI capabilities, I am not using much of it in terms of accuracy and reliability of output.

Control-M is deployed in my organization in a hybrid setup.

Control-M is on-premises in my organization and in a hybrid cloud setup, and we use AWS as our cloud provider.

My advice for others looking into using Control-M is to proceed with it.

On-premises

Amazon Web Services (AWS)

Control-M is a scheduling tool that I use primarily for monitoring and validating ETL jobs and batch jobs. My main responsibilities include checking whether scheduled jobs have completed successfully and identifying failed jobs. I verify dependencies between jobs, and when a job fails, I check the error details and coordinate with the support team. I validate the job again after it is rerun to ensure the data processing is completed successfully. Specifically, when an ETL job fails overnight, I check the job status and logs and coordinate with the support team for resolution purposes. I can verify whether the successful job completed after the rerun and check job dependencies as well. A target load job should run only after the source extraction job completes, so I verify that dependencies are current and the downstream job started at the expected time. My role includes personally monitoring logs, rerunning jobs, and performing testing validation along with Control-M administration responsibilities.

Control-M makes coordinating with the support team easier by providing job status, failure details, and execution logs in one place. For example, if any ETL job fails, I can identify the failed jobs, capture the error details, and share the relevant information with the support team instead of spending time manually checking every job. Control-M also helps to track dependencies easily. I can monitor rerun jobs and confirm that the workflow has completed successfully, reducing the troubleshooting time and improving communication between teams. The main benefits are faster troubleshooting and clear follow-ups.

The primary use case of Control-M is monitoring scheduled ETL jobs and validating successful data processing. I use it to check job status, identify failures, and ensure job dependencies are working as expected. For example, if a job fails, we resolve it and verify that the downstream completes successfully after rerun. Overall, it helps improve batch monitoring, troubleshooting, and timely completion of data loads.

Control-M has a positive impact on our organization by improving batch job monitoring, reducing manual effort, and helping us identify failures earlier. For example, we can quickly identify failed ETL jobs and coordinate with the support team to resolve issues before they affect downstream data processing. Automated scheduling and dependency management help ensure jobs run in the correct sequence and are completed on time. Overall, it improves operational efficiency and reduces troubleshooting.

We can see improvements in error identification and communication between teams. Control-M helps identify failures and resolve issues faster.

The standard features of Control-M that are valuable to me are centralizing job monitoring, automated scheduling of jobs, dependency management, and failure notifications. These features make it easier to track ETL workflows and identify success quickly. For example, I can check which job failed during a batch run and coordinate with the support team to resolve them. I can also verify that downstream jobs start only after the predecessor jobs complete successfully. This reduces manual monitoring, saves troubleshooting time, and helps ensure timely data processing.

Job monitoring is most valuable to me because it helps me quickly identify whether ETL jobs have completed successfully, failed, or are delayed. For example, if a job scheduled data load fails, I can identify the failed jobs, coordinate with the support team, and verify the job status after rerun. This helps me reduce troubleshooting time and ensure data is available for data validation on time.

The main features of Control-M include job monitoring, automated scheduling, dependency management, and failure notifications. In my daily work, I focus primarily on monitoring retail batch jobs and scheduling their execution status. For example, I can check whether the source extraction and target load jobs are completed successfully. If a job fails or gets delayed, I check the available error details and coordinate with the support team.

I have been using Control-M for the past five years, with five years of experience in Control-M and Control-M in retail testing.

I have been working with Control-M for eight years. Control-M was simply used for batch scheduling. I use Control-M on a day-to-day basis. Control-M allows me to automate the process of running the JCLs. From my perspective, Control-M works well, and I would say that it is a very good tool for building, scheduling, managing, and monitoring production workflows. Control-M is very important to my DataOps initiatives due to the specifics of the functioning of the logic of IT business processes in a bank. I am not in DevOps, but I think it is not so difficult to integrate Control-M with technologies for my DataOps and DevOps processes as things change.

That is a difficult question because I do not actually know any other tool that would be competitive with this one. I appreciate Control-M because it is a very reliable tool and it is easy to work with. I cannot imagine my work without Control-M; it is a core tool in banking systems, so I think that without it, it would be difficult to run a bank itself.

I do not see any improvement needs for Control-M at this time. There are not really any features that are missing in Control-M at the moment that I would like to see included in the future or enhanced somehow. I am not sure if this is the case, but perhaps the knowledge of how to use Control-M should be more propagated or better accessed. It can be used in other aspects than my needs, so it is also valuable to know.

I have been working with Control-M for eight years.

Control-M is quite stable; I have not had any crashes, downtimes, or performance issues with it.

I have never had a need to scale Control-M, so I cannot tell you if it is difficult because I have never had a need to do this.

I did not migrate from Broadcom CA, Redwood Technologies, or any other similar solutions to BMC. I have not switched from a different product; I started using Control-M straightforwardly.

From my perspective, to start working with Control-M, you need to learn, but it is not difficult to get a grasp of how it works.

I do not know because I did not set Control-M up. I did not have an internal team or any partners, consultants, or BMC representatives help me with the setup.

It is difficult to say how many users are using Control-M in my environment; probably over a thousand, but different roles, I would say. I have it across different locations and different departments.

Given my experience with Control-M, I would recommend it. Control-M is a good, reliable tool, and I do not think that there is much of a competitor for this in terms of banking solutions.

On-premises

Control-M is a scheduling tool that I have been using for the last three years. Earlier I used Autosys as a primary scheduling tool. When I started Control-M, it was a new experience because Autosys was over the cloud and we used to log in to the browser. Control-M is specifically for the application where we are using it now. The good thing is that there are so many connectors available.

Although I have one year of Autosys experience, Control-M presents a vast opportunity for us as a developer. Currently, I am in a data warehousing project where all the tools are legacy tools such as Informatica, SalesScript, Control-M, and database. When we are moving to the cloud, Control-M is still valid and relevant. We are transferring our data to the cloud and using Control-M as a scheduler. We are not using native cloud scheduler to date because all the developers here are accustomed to it.

We are almost using around 60 to 70% of the features. Control-M is providing us with so much capability to use during our daily problem-solving.

The good thing is that there are so many connectors available. Control-M provides lots of features, and we are almost using around 60 to 70% of them. Control-M is providing us with so much capability to use during our daily problem-solving.

When I joined this project and was very new to Control-M, there was one problem that even the seniors were facing sometimes. Suppose you are using Informatica; there are lots of Informatica developers in the market or some other tools that are very known to everyone. Even though Control-M is used by lots of people, the documentation in the beginning was very hard to search for on Google. This is why we had to reach out to people who were experienced, and it was a tough job for us because a few functionalities are not properly written in the documentation.

Another area of improvement is related to multiple versions of Control-M being used. In dev, one version exists, and in production, one version exists. In production, the stable version is used. Sometimes when we change over, there are multiple domains in Control-M such as Planning, Monitoring, History, and Forecast Tools. When we hop from one domain to another, sometimes we open a job, and the detail dialog box or detail window is not able to open.

Some features which are hidden are not properly documented in Control-M itself, or maybe documented but not properly given or described with examples. This is a problem. Sometimes we are forced to connect to senior developers who have used it for five to six years or more to learn about it.

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

There is no maintenance on my end. In the last three years, I have seen two upgrades that were done by the admin team. Control-M is using the new versions, and as a developer, I am using it.

Control-M processes about 10,000 jobs starting every day in our production environment, and adding new jobs is very simple. We don't feel any pressure on Control-M because it is processing multiple jobs in parallel.

Regarding contacting technical support about Control-M, we tried, but at that time, we didn't get any response. We reached out to our client head, described our problem, and received assistance.

As a developer, I created an account in the BMC community to get help support. We post there nearly because sometimes we need solutions very quickly, and we don't have time to connect with the guys in the Control-M help desk.

Neutral

Earlier I used Autosys as a primary scheduling tool. When I started Control-M, it was a new experience because Autosys was over the cloud.

Regarding the initial installation and setup of Control-M, I still have not installed it. I need to connect with one of my friends who are working in the ops team, as I am in the developer team. We never install Control-M here in this project.

I need to connect with one of my friends working in the ops team, as I am in the developer team. They have the access to install, uninstall, or configure anything.

Regarding pricing, I cannot comment. As a developer, this is not in my hands, and it was decided by the client.

If Control-M is selling their product to new customers who have never used anything, then who will support the new customer? The customer may not have the senior engineer who has used Control-M earlier, so the documentation matters. Control-M can improve this in the way that others have; for example, Databricks, Google Cloud, and Azure have so much documentation.

Whatever we wanted, we have it. Control-M is not executing anything; it is just a scheduler. It schedules an Informatica job, and Informatica is running on its operating system, managing all the logs, and showing us that the job is completed. I have not seen any lagging. This can be answered by the ops team better because as a developer, I own a few applications, and when they start and end, my duty is done. Overall, I would give Control-M a rating of eight out of ten.

On-premises

Other

We are a cloud service provider, and we have been using Control-M for integrating and automating the orchestrating applications in the data workflow in our production. This is the main use case for our flow.

We are using its cloud version, Helix Control-M.

Helix Control-M has helped us schedule the jobs and manage our workload. We save time in running the jobs. There is no impact on the software even if I schedule a hundred jobs at a time. It can accommodate all kinds of jobs. It helps to meet our large-scale requirements.

Helix Control-M’s ability to build, schedule, manage, and monitor application and data workflows in production is good. It is pretty straightforward. It integrates well with different applications, such as AWS, GCP, and various cloud providers, enabling job scheduling directly from the Helix Control-M interface without any agents. Integration is very easy.

We have a single pane of glass for scheduling and viewing job status. We get all the details in one window. We can schedule everything in one window. We did not have any downtime with the Helix Control-M. All the jobs have been running perfectly. Everything is smooth and straightforward.

We are mainly using the AWS Cloud, and we also have some GCP services. We can monitor all the details under the History tab. We can see all the past jobs. 

Helix Control-M gives our company’s business users visibility and control over their jobs and frees up IT personnel for other tasks.

Helix Control-M is very critical for our business. We rely on it. We do not want any other scheduler. It provides us with everything.

Helix Control-M has contributed to the overall stability of our applications and improved user experience. It has taken away some of the administration work.

The flexibility of Helix Control-M allows us to manage tasks efficiently. The user interface is comprehensive and lets me view all my jobs on one page, monitor everything, and access the job history. The UI is superb and flexible to use.

Scheduling multiple jobs at a time is a standout feature. 

There should be an expansion in storing more data as it currently provides data storage for only up to 60 days. 

There can be some complexities with the UI part, especially with the advanced features. Other than that, it has been pretty good.

I have been using it for almost two and a half years.

The stability of the Helix Control-M solution is good. I would rate it an eight out of ten for stability.

We also have access to their support. If we face any issues, we get support from them. Everything is good and working as expected.

Helix Control-M is scalable. It is being used by many people in our organization.

We have more than a hundred jobs running, and we have almost eight people managing it. We also have 3-4 end users using it.

The technical support is very polite, helpful, and available 24/7. I would rate them a ten out of ten.

Positive

Before Helix Control-M, we used different solutions. We previously used IBM Workload Automation but switched to Helix Control-M because it provides a comprehensive solution for everything and is very manageable without needing a dedicated person. Anyone can learn it. Its learning curve is very small.

The migration to Helix Control-M was straightforward. We did not face any issues.

The initial setup was straightforward. It took about three or four months to settle down. It is also not difficult to maintain.

We received support from BMC tech support and did not require any third-party consultants. We had six or seven people for the deployment of the solution.

The main return on investment with Helix Control-M has been a reduction in downtime and minimization of manual interventions, which has improved our operational efficiency.

The pricing is moderate, not too low or too high compared to other solutions.

We evaluated multiple solutions, including ActiveBatch, before choosing Helix Control-M.

The pricing was similar, but we found Helix Control-M better in terms of job automation and features. Their support was also very good. We got help from them with the orchestration and migration.

Before implementing the solution, thoroughly try out how it works in your current environment. 

My overall rating for Helix Control-M is an eight out of ten.

Hybrid Cloud

My main use case for Control-M so far is exploring what I can use it for currently.

I attended an event today and gained several insights about Control-M that I will explore further.

Regarding my experience and expectations with Control-M so far, it has been very insightful and positive.

We manage the integration and sequencing of data processing across diverse platforms and cloud environments by using Git and the Azure portal.

Control-M is not yet being used for AI or ML workloads, but we may consider using it for these purposes in the future.

We are not currently using Control-M to facilitate the integration of Kubernetes or cloud-native workflows with traditional batch processing.

We are not currently using Control-M to address compliance requirements, though we may consider it in the future.

My organization is not yet using Control-M, but I believe that after others in my organization see its capabilities, we may adopt it.

I think Control-M could have a positive impact by increasing productivity, as it has a very good UI and debugging features that would make work faster.

Based on what I learned and saw today, the best features Control-M offers are its ease of use and numerous tools and capabilities. The features I can use for software development and software engineering are very good and make tasks easier.

I found the debugging and UI tools to be very useful for development and debugging work.

Control-M's UI stands out as very user-friendly and more convenient than other tools I have used.

Regarding Control-M's AI capabilities, I think it is very important to have better governance because organizations like ours should not populate client-specific data or documents. Control-M is very good at maintaining secrets and acts ethically, making it excellent in terms of security.

Based on what I have seen and heard so far, Control-M's accuracy and reliability of output are very good, as it gives straight-to-point answers when it comes to precision and accuracy, providing straightforward answers and content-relevant information.

Based on what I have seen and learned so far, I believe Control-M is stable.

From what I have gathered, Control-M's scalability is very good, ranging from moderate to high.

During this event, the customer support was friendly and provided a good experience.

We would use Codex and Claude for automations before considering Control-M.

My organization would prefer a hybrid cloud or a public cloud for deploying Control-M since we typically use these cloud environments, but it is not yet deployed. Today's session may prompt our organization to give it consideration.

Our organization currently uses Amazon Web Services (AWS) and Microsoft Azure.

I have seen nothing in terms of return on investment from similar tools as of now.

I am still in the evaluation phase regarding other options I evaluated before choosing Control-M.

I chose nine out of ten because of the knowledge I gained from today; it is very good and convenient to use. I believe I would give it a ten out of ten when I start using it and practice with it in the future.

Control-M is a very good solution for use in today's world; it is quite convenient for our development tasks and makes it easier to work.

Hybrid Cloud

Amazon Web Services (AWS)