Control-M Reviews

I mainly use Control-M for scheduling jobs according to my requirements, which allows me to include holidays or exclude Saturdays, Sundays, or any specific time.

I also use cyclic jobs that run in a recurring period and can set up prerequisites before the job runs.

I can implement a File Watcher to establish a rule that a particular job can only run after the upstream job is completed.

I have created several new jobs using these capabilities.

Within Control-M, I use smart folders and jobs, and I can approach scheduling the way I want, so I have used it fully from start to end.

Control-M is straightforward for building, scheduling, managing, and monitoring production workflows.

I use the XML side for configuration, which requires importing, and I find it user-friendly.

Control-M has been used for building, scheduling, managing, and monitoring production workflows, especially at JPMorgan Chase Bank where most production support is monitored through Control-M.

I worked as a developer, developed jobs, and sent them to production, and the process was seamless.

My favorite feature about Control-M is the rule-based calendar feature.

The initial deployment of Control-M is straightforward, as it involves a simple installation of a Control-M agent within the server.

Control-M demonstrates strong scalability.

My application alone uses approximately 65 jobs, and for each folder, there are thousands of jobs that can load immediately in production.

When using a filter, the search is quick, and overall scalability has been excellent.

After migrating to Control-M, the positive effect on business-critical applications is evident: whenever a job ends successfully or fails, notifications are sent immediately.

These notifications go to EventBridge, alerting the team to any critical jobs.

High-priority jobs trigger alerts to engage developers immediately, ensuring there is no delay in response.

One area for improvement in Control-M could be in the logs, as they only show when the job started and whether it ended successfully or not.

Since the Control-M agent is running on the servers, we could pull up logs and display the actual error to aid in debugging.

I have been using Control-M for approximately eight to nine years in my career.

Regarding stability, I do not experience any lagging, crashing, or performance issues with Control-M.

Control-M demonstrates strong scalability.

My application alone uses approximately 65 jobs, and for each folder, there are thousands of jobs that can load immediately in production.

When using a filter, the search is quick, and overall scalability has been excellent.

I have never contacted technical support or customer support from BMC regarding Control-M because we have sufficient in-house expertise to share knowledge about it internally.

I started on TWS, Tivoli Workload Scheduler, which is an older tool with a poor user interface.

After transitioning to Control-M, I have been very satisfied with it.

I have not identified pain points until now because the use cases I addressed were fully satisfied by Control-M's capabilities.

Whatever use cases I needed, they were fulfilled by the product.

I used Tivoli Workload Scheduler earlier, but now the company has standardized on Control-M without using any other schedulers.

The initial deployment of Control-M is straightforward, as it involves a simple installation of a Control-M agent within the server.

Only one person is required for deployment, and it can be completed without needing a team.

For both job deployment and software installation, one person typically handles it, as we use an automation process with no manual work, making it a self-service operation.

I have personally used TWS as an alternative to Control-M.

I prefer Control-M over TWS.

The biggest difference between TWS and Control-M is that TWS has a poor user interface, while Control-M has an excellent user interface and alerting capabilities.

TWS requires monitoring on one page without navigation directions, whereas Control-M uses smart folders with parent and subfolders, maintaining a clear graph structure and allowing the creation of custom workspaces.

Regarding data pipelines, I have not explored integrating them via Control-M.

Non-technical users or business users do not need to use Control-M, as they primarily rely on developers or application support.

Currently, all employees at JPMorgan use Control-M for everything except mainframe jobs, which are monitored and developed through Control-M.

For maintenance, a patching team manages it, and I do not experience any downtime with Control-M.

I might not notice maintenance communications since they could be performed behind the scenes or during off-business hours.

I would rate this review an 8 out of 10.

My main use case for Control-M is job scheduling. I use Control-M for job scheduling by scheduling jobs for the asset team, like OS jobs, MFT jobs, and AFT jobs. I exclusively use Control-M for scheduling.

The best features Control-M offers include monitoring, planning, and forecast. Planning stands out the most for me in Control-M, as it helps me to schedule jobs.

Control-M has positively impacted my organization by allowing us to automate a lot of manual activities, so we are saving time.

Control-M can be improved with GUI features such as job failure monitoring, where the duration can be increased from 30 days to one year so that we can monitor long durations of job failures.

I have been using Control-M for 11 years.

Control-M is stable.

The scalability of Control-M is good.

The customer support for Control-M is fine.

Negative

I did not previously use a different solution.

My experience with pricing, setup cost, and licensing indicates that it is cheaper than other automation tools in the market.

We require five staff members for deployment and maintenance, and they all are consultants.

I have seen a return on investment, specifically in terms of money saved. We are saving a lot of time, as many activities that used to take around three to four hours by manual activity have been reduced to 30 minutes to one hour.

My experience with pricing, setup cost, and licensing indicates that it is cheaper than other automation tools in the market.

Before choosing Control-M, I did not evaluate other options.

My advice to others looking into using Control-M is that it is easy to use, flexible, and stable. The features in Control-M are good, and the GUI of Control-M is actually very fantastic.

Currently, 500 users are using Control-M in my organization, where the majority of them are from the application team and a few are admin and schedulers. Control-M is currently used extensively, and while we do not have plans to increase its usage, we are using Control-M in different domains.

The biggest lesson I have learned from using Control-M is that it makes automation easy. It is easy to integrate Control-M with technologies for my data ops and DevOps processes as things change. I have automated activities on the Linux server while integrating with Control-M.

I would rate this product a 10.

Private Cloud

Amazon Web Services (AWS)

My main use cases of Control-M involve workload automation, with two key areas being financial reconciliation and supply chain management. In financial reconciliation, a global financial services company pulls data from all its divisions around the world to perform end-of-day, end-of-month, and end-of-quarter reconciliation across a range of technologies, teams, and borders.

In supply chain management, manufacturers with retail stores need to ensure that the right stock is in the right places, which can be complicated. The third main use case relates to integration with SAP, making existing PA environments cheaper and less service-heavy. Those are the three main ones in my customer base.

My customers use Control-M to orchestrate workloads across multiple environments. Control-M orchestration is capable of handling complex data pipelines or analytic processes, which is key for some of our financial services customer use cases and is a relatively core part of their requirements.

My banking customer that moved some capabilities to the cloud uses Control-M for both on-premises and cloud technologies, so that's my awareness regarding the creation and automation of data pipelines across those environments.

The features of Control-M that I find most appealing, and that I've heard customers appreciate, include the file transfer capability, which is very unsexy but fundamentally important. It's what it's all about—extracting data and moving it to different places.

The relationship between Control-M and my clients' DataOps and DevOps initiatives is complex. Most of our customers have their DevOps initiatives somewhat divorced from the Control-M elements. However, this is slowly changing as DevOps starts to incorporate both customer-facing aspects and the internal legacy parts of their business. They are gradually integrating, and that agile way of working is coming closer together.

The measurable benefits or improvements my clients have seen with Control-M relate to compliance, particularly in financial reconciliation. There are significant financial penalties for errors in this area, so it's crucial to develop a robust integration with ITSM systems to ensure that tasks perform as intended and meet the right SLAs.

Control-M can be improved by continuing the trend of being both a mature product and one that is not standing still, as evidenced by the ongoing improvements we've seen. The file transfer piece is particularly popular, and it's essential to keep up with the demands that customers place on it.

I suspect a lot of my customers aren't pushing the boundaries of what Control-M can scale to, but the job scheduler approach allows for immense scalability. Many of our customers are only beginning to explore its capabilities.

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

I don't believe any of my customers have reported issues around the availability of Control-M regarding stability and reliability.

I suspect a lot of my customers aren't pushing the boundaries of what Control-M can scale to, but the job scheduler approach allows for immense scalability. Many of our customers are only beginning to explore its capabilities.

I haven't heard any complaints about BMC's service team support; as far as I know, customers feel comfortable about it. Of course, I can't speak from personal experience.

Neutral

There is a competitor to Control-M that many of my customers consider; the big one is IBM's IWS. There is some anecdotal evidence of dissatisfaction among customers regarding support since it has moved to HCL. I recently spoke to someone about exactly that scenario.

The overall experience of the migration and deployment process for my customers tends to be a horror show because migrations are critical and touch everything. The biggest challenge people face is unpicking the complexities involved. Thus, it's often hard to simply migrate, especially while maintaining a good relationship with the existing vendor.

On the topic of pricing, setup cost, and licensing for Control-M, everyone moans about it. We work with some customers on optimizing their job structure to deliver proper value for money. This is significant work, as getting value for money is a challenge we constantly address.

The biggest return on investment for users of Control-M in the financial sector can be fairly straightforward: you can easily state how much performing tasks manually would cost in person-hours. By avoiding financial penalties from regulations, the business case essentially writes itself. In manufacturing, it's more complex, as you look at how to minimize manual costs and whether Control-M helps reduce customer churn and ensures stock is in the right location. Extracting this information aids in making the business case.

On the topic of pricing, setup cost, and licensing for Control-M, everyone moans about it. We work with some customers on optimizing their job structure to deliver proper value for money. This is significant work, as getting value for money is a challenge we constantly address.

There is a competitor to Control-M that many of my customers consider; the big one is IBM's IWS. There is some anecdotal evidence of dissatisfaction among customers regarding support since it has moved to HCL. I recently spoke to someone about exactly that scenario.

In my company, zero users interact with Control-M because we don't actively use it; we just sell it. My customer base ranges widely, with some cases having a small batch team of a few dozen users up to hundreds, probably more in rough figures. I wouldn't have huge visibility on that.

I have heard of the Control-M Python client or API very recently. My experience selling the Control-M Python client or API is relatively new to me. It's not entirely new, but it hasn't come up much in my customer base. However, as DevOps and Control-M are becoming better together, I am seeing more of that.

Regarding metrics or data on how my customers perceive Control-M, I don't have any off the top of my head, and I probably would be privileged to know.

My advice to a company considering Control-M is to bring us in to help with the assessment work. Go through a value stream exercise to clarify what you're trying to accomplish and examine the entire end-to-end process. Control-M and workload automation is a solved problem; it's something you should buy rather than build yourself. That would eliminate undifferentiated heavy lifting. Certainly, we can assist clients with automation and value chain assessment, especially beyond the BMC space, which often presents a messy and complex landscape. I would rate this product a 9 out of 10.

Control-M is used to run Oracle scripts with scheduled jobs including monthly, weekly, and yearly schedules. Around 50 or more jobs are run every week. Control-M connects to the database, triggers all procedures, performs the operation, and generates the final report. The log is sent to mailboxes detailing how the process went, any issues, or any errors. If there are issues, the mailbox is checked; otherwise, a message indicating successful completion is received along with statistics such as how much time the process took and which processes were run. Jobs are scheduled once, Control-M jobs are created, timing is set up, and the jobs fire automatically at the particular time.

Control-M is used to connect to Oracle products, and through Control-M, a Tableau dashboard is maintained. Most of the scheduling jobs use Control-M to schedule. Control-M helps all products, making it a utility that can be used wherever scheduling features are needed. It is not just for DevOps, databases, or front-end applications; it can be used anywhere without manual intervention to perform particular activities. Wherever there is an opportunity for scheduling jobs, Control-M is the first option.

For migration, Control-M is considered very good. Once all the source and target details are configured in Control-M, it can automatically migrate data. It requires proper configuration and specifying the necessary changes for target technology along with the source system scripts. If properly configured, the complete migration can be triggered end to end. Data migrations and reporting, along with all scheduling activities, can be efficiently managed.

The best features in Control-M include sending emails to mailboxes after the process is completed and providing proper acknowledgement reports. The timing is impressive; it connects very fast and performs activities efficiently. The UI is very friendly, making it easy to configure jobs in Control-M. If core technology scripts are available, creating Control-M jobs is a five-minute task. The GUI is very friendly, which simplifies task assignment, scheduling, canceling, and all these operations, making it easily navigable.

Every week, 50 jobs are run using Control-M. If those 50 jobs were being run manually, it would take more than a week. Through Control-M, the jobs are able to be scheduled within two days, saving around five days of effort.

Before Control-M, jobs would be run on Friday evening so that the process would end by Sunday night, allowing the business to start on Monday. Without Control-M, everything would have to be run manually throughout the week. Thanks to Control-M, around five days are being saved. Otherwise, old data would be received for the current week's business, but now the latest data is received.

Control-M has room for improvement in displaying dashboard-like graphical reports once processes are completed. For example, after scheduling 50 jobs, if a dashboard showing the completed scripts, status, and time taken is displayed within Control-M itself, it would be very helpful. Currently, mailboxes are checked for reports; if it were in Control-M, anyone could check it. Only those configured with specific mail IDs receive emails, so if a few members are not set up, they will not see the reports. If it were available in Control-M, those users could directly check the dashboard.

Control-M has been used for the last two years from the beginning of the project level. Earlier, it was already there in Control-M that the client was using.

The same score for stability is a nine out of ten.

Control-M is capable of handling a large volume of processing if the necessary memory space is provided to the server.

Great support is received, with a rating of nine out of ten.

Positive

Control-M would definitely be recommended because it saves a lot of time. If everything were being done manually, it would take a lot of time to run and validate scripts. If everything is configured in Control-M, even non-experts like front-end staff can trigger jobs, making it simple. It is a one-time configuration, and anyone can trigger it. That is the best part; significant time is saved, and there is no waiting time; the next process starts immediately once the current one is completed. If dependencies are set in Control-M, it starts the next task automatically. That is why Control-M is highly recommended for scheduling.

The client is a big enterprise client.

Control-M requires occasional maintenance, maybe yearly or once every six months for upgrades. A Control-M team manages activities such as maintenance every six months or once a year, including cleaning up scripts or memory.

Around 15 members are using Control-M.

The overall review rating for Control-M is ten out of ten.

On-premises

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.

Neutral

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

Other

I work with Control-M from a commercial aspect and engage with IT and operation teams across different industries, which gives me direct exposure to how Control-M is used in real production environments. My role is to deliver tangible value to these teams.

The valuable features of Control-M depend on the specific customer needs. Some customers have business-critical processes, strict SLAs, and hybrid or multi-cloud environments where Control-M provides end-to-end visibility of all these processes. Control-M also offers different modules, such as MFT, which allows users to transfer files with the tool. As a commercial professional, I cannot personally attest to specific features since I do not typically use the tool directly, but I can share what customers have told me they value about the product.

As a commercial professional, I think one of the downsides of Control-M is that not all people know they can use a tool such as Control-M, and they think that Control-M is going to be very expensive, which is the reason why they don't want to use it or seek more information about it. However, when they are accustomed to using this type of tool or Control-M as a scheduler, they feel better with it and with their role inside their enterprise. For example, if they don't have any scheduler, they don't know that they can use a scheduler to automate different business processes. When they recognize that they can use this type of tool, one of the objectives is to reduce costs. They may spend money in the short term, but in the medium or long term, they will probably have more benefits than risk.

Control-M has everything that a person needs because the problem is not high cost. Control-M is available on-premises and in the cloud, and they are having more apps every week with the app integrator. I don't have anything that I dislike about Control-M. Possible areas for improvement could include documentation, configuration, and pricing. Being more flexible and having out-of-the-box reporting for business stakeholders would be beneficial. Continuing to simplify licensing and packaging for smaller customers would also help improve customer conversations. Reporting is often mentioned as an area where Control-M could continue to evolve. Many customers would appreciate more out-of-the-box business-friendly reports. Control-M has operability with SLA-focused reports, but developing something with less customization would be better.

I have been using Control-M for more or less two years.

I think that some instability is normal because everything is in the cloud, and I can remember a few months when the AWS cloud crashed. If you see the SLA reports or responses from different customers, they are very happy with the tool. Control-M achieves more or less 98% or 99% uptime in the cloud, which is a fantastic rate. I think 100% is impossible to achieve, and 99.8% is a good number.

Control-M, developed by BMC, which was previously part of BMC Helix and is now BMC Software, is focusing on Digital Business Automation processes. They are developing many different modules in Control-M, and the scalability is fantastic. Probably in a couple of years, Control-M is going to be the best scheduler. Currently, they are competing with other schedulers such as Redwood, Broadcom, and Stonebranch, but in a couple of years, maybe one or two years, Control-M is not going to have any competitors.

I have used technical support from BMC when we need to do demos for instances in the BMC tool. The technical support team are very good professionals and they do their jobs excellently. Since I don't use Control-M directly, if I have a problem with Control-M, the technical team from my enterprise would need to talk with the technical team from BMC. I usually talk with the commercial team from BMC rather than the technical team. I talk with the technical team when I need to make a demo, proof of concept, or proof of value, and we need to customize the future instance for the client. If I need to rate the technical support from BMC, I would give them a 10 because whenever I want to do something with them, they answer me, and I am very happy with them.

Positive

I don't use any alternative schedulers. I know that you can talk about Redwood, Broadcom, or Stonebranch, but I don't use any one of these schedulers.

I don't have a lot of contact with deployment. Probably if I think about some customers, they tell me that there is also interest in simplifying upgrades and environment standardization, particularly for organizations with multiple Control-M instances. If you talk with a small customer, they are going to be happy with deployment, upgrades, or the environment.

Control-M has an upgrade more or less every year or every two years. If you want to use the latest upgrade, you need to upgrade your tool.

The implementation team depends on the person doing the deployment.

The current pricing is good. Other vendors such as Broadcom are increasing their prices, so right now, Control-M is not one of the highest-cost schedulers. My customers have never told me anything negative about the pricing or licensing. BMC can be very amenable with the pricing of the tool. I have small customers, and I think that is a good point of view because they think they can't have the budget for a tool such as Control-M, but they do have the budget. Control-M is a tool for every kind of customer. You can sell Control-M for 15K on-premises and you can sell it for 7 million or 11 million. I think that people need to change their thinking because Control-M is not just an expensive tool. It is a tool for everyone, for every enterprise.

I would rate Control-M at nine.

Amazon Web Services (AWS)

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.

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