Control-M Reviews

I've never worked in a company where we weren't using it, so it's hard to say how it improves our organization. Our Oracle Database backup teams used to do this all themselves via cron. They've automated what was done by cron with Control-M. Other than that, everybody's using it.

It saves us time. Instead of 800 applications internally doing their own thing, we centralize it into one location where there are notifications. Taking the power of economies of scale into one point of focus, it saves us money for sure. We turned a company of mom-and-pop little fiefdoms all over the place into a company where things are centralized in one location.

Monitoring is a valuable aspect of it. The monitoring tool is very good. It's very easy for expert and entry-level users to use on short notice. Also, the usability is good.

The reporting tool needs a major-league upgrade.

I also would like not to have to reach out to a third-party application company to do automated notifications. Right now, we still have people manually calling people and emailing people. There's a company called xMatters - and there are others - that has an API through Control-M that can automate any aspect of failure management. I'd like to see it build right into the product. I'd like to see a better notification product.

In some parts of Control-M the stability is good, in some parts it's not so good.

We're going to see the scalability soon when we upgrade. 

Most of the time we don't get the answers we're looking for. That's why we use a consultant company.

It works on task-based licensing.

Procurement may have looked at other products. But from our perspective, they probably would have scared the living heck out of us if they had told us they were looking at other things.

You have to talk about it more in terms of how Control-M fits into the scale of other products which BMC offers for what you're doing. It's got Helix, cloud management, ITSM, etc. BMC offers the whole scale - everything. We don't choose to use it all. But from another prospective, it's a real positive that they have this scope, that they can handle everything a corporation could throw at it.

I would like to see us use more things such as Helix. From that perspective, I would recommend it because of all the product offerings and because a lot of the approved vendors, which work directly through BMC, really make the experience a lot better.

We learn things every day about the product and the availabilities. We work in an IT environment with inquisitive people. There are millions of options available, parameter-wise, within the system and I learn something new every day, by working around smart people and intuitive people.

In terms of how the solution affects business modernization initiatives, this is all somewhat new for us. We're starting to go into a little bit of the DevOps and the Workload Change Manager, and the cloud chat-box. We're just starting to get into things like that with BMC Control-M.

I would rate the solution at eight out of ten. We've had massive growth in the last year to two years because of company acquisitions. We've added a lot of big-data processing and a lot of other processing and it's handled it quite well. We really haven't had any serious outages in quite a long time, even through the large growth we've had. We've doubled the work and it's handled it seamlessly. It's just that the reporting aspects are poor, because management always wants to know things. It's hard to get at tangible numbers without doing a lot of additional work outside of the system.

Control-M has a huge number of features, including:

• Cross-platform support
• Integration with applications such as Oracle, SAP, FTP, Hadoop, JMS, and many others.
• A GUI with various filter options that allows you to manage jobs from one screen.
• Add-ons such as BIM, Reporting Facility, and Forecast.
• Automated error handling allows you to define actions to be taken depending on the exit status of a job.
• Web-based and mobile applications allow you to manage Control-M from anywhere.

Before implementing Control-M, SAP or FTP related jobs were triggered using scripts. With Control-M, these jobs can be triggered using modules already integrated into Control-M, reducing team effort.

Also, Forecast and BIM give us a clear picture of batch job deadlines and alerts us of schedule overruns.

The cost of Control-M is a major factor. It is difficult for small-scale organizations to use Control-M as a solution.

I have been using Control-M for 10+ years and have no issues to date.

We have not encountered any stability issues. Control-M provides a highly stable environment. Fix packs are released regularly and immediately upon discovering bugs.

We did not encounter any scalability issues. Control-M can handle multiple servers, multiple cross-platform agents, and a large number of jobs easily.

BMC technical support is great. I rate it 10 out of 10. We have received immediate help with issues.

Previously, job scheduling was done internally using a SAP scheduler, Windows Task Scheduler, and cron. However, they all had limitations and we needed a single interface to handle different types of scheduling.

Initial setup and installation of Control-M does have challenges, but BMC has good technical support. Related documentation is also available online. Once you are familiar with these, setup becomes straightforward.

Pricing is somewhat on high side. But it’s recommended for bigger organizations.

We evaluated AutoSys and IBM Tivoli Workload Scheduler, but they didn’t offer anything close to the functionality that Control-M offers.

If you need a one-stop solution for all your automation needs, Control-M is your answer.

We use Control-M to provide business services to our customers. The use cases involve Hadoop, a lot of file transfers, and SQL scripts. In our business, automation is used for many things and we use a lot of the Control-M modules. For example, we connect to SAP, with databases, Hadoop, MFT, Informatica, and other technologies.

What we do relates to many different business services in a retail environment.

We have hybrid deployment; over the past two years, we have had a mix of on-premises and cloud-based implementations. Ultimately, we are moving to the cloud. We are using AWS, GCP, and Azure.

The main benefit is that Control-M can work with almost all of the applications that are on the market right now. We work with technologies including Hadoop, Informatica, all kinds of databases, and file transfer with MFT tools. The real potential with Control-M is that it can be used for everything you want.

It is really important that our clients can manage their own application workflow with full autonomy. Our customers are using this capability a lot and it helps because we don't need to be present when they want to perform a simple task. It's better for them because they don't need to wait to ask or to have something changed. They can just do it themselves. Also, it's better for us because we have more time to do other things.

The expanded capabilities in version 2020 for planning and monitoring have had a positive effect on our clients' operations, as well as our own. It saves a lot of time when it comes to developing and implementing things. As a result of saving time, both us and our clients are saving money.

Control-M has definitely helped us to achieve faster issue resolution, although it is difficult for me to estimate how much by. We don't have metrics that are suitable for tracking this kind of thing.

The best part about this product is that it has a lot of features. Control-M doesn't limit us and we can use it for a lot of things.

Control-M is easy to install, use, and maintain. It is easier to work with than other products.

The web interface hosts a lot of videos and webinars and I really appreciate this because I find them very helpful. They have tutorials that explain how to approach the new technologies and explain how things can be done using Control-M. This is something that I use a lot.

The Application Integrator is helpful because not all applications have a module available in Control-M, and we can use this feature to create them.

When it comes to supporting cloud services, Control-M is a bit slow. We are not advancing with the technology because we don't have the modules that can interact or use the new application services provided by the cloud technologies. BMC has been telling me that they are working hard to be more aligned with these new technologies, but they are a bit slow. Consequently, we are having a few issues when it comes to implementing Control-M. Some services that are being offered, such as Databricks, have been a problem.

The documentation is something that needs to be improved. Years ago, the documentation was very good, and I don't understand why but the documentation is no longer as good as it should be. For example, if I need to install or upgrade Control-M Enterprise Manager or Control-M server, the only information that I have in the documentation are things like "Execute this and follow the instructions on the screen".  What it doesn't tell you is what will be needed for the process. For example, you may need to enter a password or select a source, but you won't know what these parameters are in advance.

Also, it is different to find what you are looking for in terms of documentation. For instance, if you visit the Control-M download page, you see several tabs. There is a tab where you can download software and another tab where you can download patches. This is perfect. However, there is another tab for the documentation but there is never anything there.

With any Control-M product, it is hard to find the documentation. The reason for this is that they are moving all of the documentation online, in an HTML format. The problem is that it is hard to download documentation in this format. In particular, if it is a specific part that you need or a certain module, then it would be much easier to have a PDF version like they used to have. Consequently, it is more difficult for us to pass the documentation to our internal teams.

For example, if we are trying to configure a module for Informatica or SAP, it's hard because we don't have PDF documentation. We need to go online but it is difficult because it is very hard to find what you are looking for.

Another area of improvement for Control-M is the version release lifecycle. Prior to 2018, we had the same, main version of Control-M for two or three years. Since 2018, they have been releasing a new version every year. There was a 2018, 2019, and 2020 version. It seems that these new versions are being released in an unfinished state because we are seeing a lot of bugs. Historically, it has been very stable, but from a point between two and three years ago, it has not been so much so. It seems that the problem is that the versions are changing too quickly.

I have been using Control-M for nine years.

There are some limits to scalability in terms of cloud integration. There is some integration with cloud services but it is very simple. It is called the Application Integrator Module. This is a very good feature but the problem is that if we have to interact with cloud services, we need to create all of these modules on our own. We are paying a lot of money for a product where we have to create our own modules, which is not perfect.

It is very good that we have the Application Integrator available but for services that are being used by a lot of companies, we need official support from BMC.

I would rate the technical support an eight out of ten.

We have been dealing with BMC for several years and when you consider the support from a few years ago, the response that we received was more technical and more accurate regarding the problem that we were having.

As it is now, more and more we are seeing that the customer support has to rely on the product development team to resolve the issue. This is because there are a lot of bugs in the product and customer support cannot provide a solution for these. Instead, the problem has to be fixed by development, and then a patch is released to solve the problem.

For this reason, I am rating the support an eight instead of ten.

We have had cases where our clients migrated to Control-M from a competing solution. In fact, we did a migration last year from TWS, the Tivoli Workload Scheduler from IBM, to Control-M using the conversion tool. The tool was very important because it reduced a lot of work.

The problem is that the conversion was not as good as it should be. I estimate that we had to modify 90% of the jobs because the conversion was not good enough. It was still important because it would have taken a lot longer to create all of the jobs from scratch. That said, it was not perfect, at least that was our experience with migrating from TWS.

We were using TWS and another one that is called Visual TOM. It is another product that is similar to Control-M. These are both scheduling products, but Control-M has tons of features that the other ones don't have. They don't have the modules, the plug-ins, or the Automation API. They are stable and they are good, but we can't use them like you use Control-M because Control-M permits us to perform many more things. Unfortunately, with the many more things that you can do, it does introduce more opportunities for failure. However, this is true of any feature-rich solution. The more complex it is, the more prone to error it is.

Control-M is easy to install and maintain. There are not a lot of steps required to upgrade or downgrade from one version to another. With other products that I've been using, it is difficult and complicated to upgrade because there are a lot of confusing steps. But with control-M, you need only follow the onscreen instructions.

The length of time required to deploy depends on the customer. The scope and complexity of the client's requirements dictate the amount of time it will take to complete. For example, we can deploy for a smaller customer in one week. However, for a large retail customer, it could take a month to complete.

We have one client right now, where we are upgrading from Control-M 2018 to 2019, and it is going to take us almost three months to complete. Part of the reason it takes this long is that when you try to upgrade a production environment, it's really difficult to get a window to perform the upgrade or the installation or the modification. That said, it's still easier than many other products.

Pricing varies depending on which components and modules you are using.

My advice for anybody who is considering Control-M is that I recommend it. Although it's not perfect, it is relatively easy to use and maintain.

I would rate this solution an eight out of ten.

We use this solution for automating workloads across traditional data centers, the cloud, SaaS offerings, and various other Enterprise software packages.

It is allowing developers and product owners to create complex workflows that may encompass several different products or technologies and have it all visible, monitored, and managed from one place.

The Single pane of glass view has helped us to see the big picture.

The auditing and archiving capabilities have helped us maintain compliance and provide for a single place to look for errors, check historical runs, etc.

We have increased efficiency by reducing the number of people needed to watch and react to processing.

The simplified integrations and scheduling across various products was a big win to reduce silos.

The Automation API has opened up a world of possibilities for us, including the ability to create workflows on-demand using traditional DevOps tools.

The most valuable feature is the Automation API - Jobs as Code. This is the future of workload automation. It brings Control-M into the DevOps sphere, and they are focusing a lot of effort with monthly releases of this product.

The Web interface is coming along but still has some missing pieces. Today, you must still rely on the full GUI client to do everything you need. The next major release needs to focus on the lightweight web client.

I'd also like to see more out of the box support for Docker, etc.

We have been using this solution for more than sixteen years.

This solution is highly stable with a good customer support team.

This solution is highly scalable.  We can run one job or a million jobs, with ease. We've never had an issue.

Technical support for this solution is top-notch. Many of the folks that I email have been there for years! That says a lot.

Prior to using this product, we used homemade solutions and we outgrew them.

The initial setup of this solution is straightforward, but for new users, I would recommend engaging a third party to help you set up and learn the ropes.

We used a vendor team to assist with the deployment.

Over the years we've saved countless man YEARS. We have also avoided having to buy additional products for scheduling and integration. The list really does go on and on.

Pricing can be steep, but you get what you pay for. If you are just concerned about cost, you are going to miss the big picture because Control-M has features that are light years ahead of the competition. Don't save a nickel to spend $20.

Before choosing this product we looked at Computer Associates (CA Technologies) and Tivoli.

Control-M is light years ahead of any competitor we have looked at.

You can try it without buying it. I would suggest checking out the workbench at: https://jobsascode.io

This is a free version of the Control-M package that is perfect to take for a spin.

We use it for our job automation, running jobs daily, monthly, and annually. So, it is all automation.

We use another product, which is a BMC competitor, and we were able to integrate the two product. Therefore, if a job fails, it is automatically contacting the development team who is in charge of that job.

Automation is its most valuable feature. It comes down to if you schedule a job, then it runs on its own. You don't need to have an operator manually start a script, start a mainframe job, etc.

I love the usability. It works. 

If a job fails, that development team is notified right away, which improves reliability. Previously, it was on the operators to notify the developers that their job failed, erred, or aborted. Now, it's all automated.

The technical support is great. They get it back to you right away. As soon as you open up a ticket, they are on it. I am happy with them.

We had a BMC competing product, then we integrated it with Control-M.

The initial setup was complex, because I wasn't used to it.

We used a consultant for the deployment. We had a great experience with them.

We are not yet using the solution's application workflow orchestration.

We are not using it for business modernization initiatives yet. 

We don't use any other BMC products.

We're not fully entrenched in Control-M yet.

Our primary use case for Control-M is to order the jobs we have, like database entries and processes that need to be run in Unix or any other environment. With Control-M, we can run a set of flows at a specific time, like maybe on the fourth of every month or every second Sunday of the month.

The Control-M feature I find the most valuable is the ability to configure a lot compared to a contract. 

An issue we have run into in our lower environments is that Control-M can log you out frequently. This happens when you have a lot of applications running. Maybe it's just a configuration issue, but this is a pain point that would be good to look into. 

I have been using Control-M for a couple of years now. 

Control-M is a stable and reliable solution. 

I have not seen any issues with Control-M in our production environment. However, in the lower environment, we can see frequent log-outs. That could be an issue with how much they have allocated. 

In our organization, the development team uses it, as does the bank team. They monitor it. If a job fails, for example, Control-M sends out a notification and the team can take a look at what happened in the logs. They can do it on the fly instead of dealing with the issue later on. 

As soon as you have an issue, a ticket is created and the tech support is quite responsive. 

I did not set up Control-M in my organization, but the setup is straightforward. You just log in with your credentials and everything is already setup for you. You can access things in line with whatever authorization you have. 

I would recommend this solution because of the ease of use. To work with it, you do need to understand it and know how to configure it. But, once you do, you can take advantage of many features that are helpful. 

We use this solution for enterprise workload automation in the financial industry. We schedule and monitor hundreds of business-critical processes.

We also leverage the Managed File Transfer capabilities of Control-M to handle our file transfers securely & efficiently. Most of our tasks also deal with databases, and Control-M's purpose-built module for the databases comes in very handy when handling database components. It adds value with its capability to execute tasks natively and bring more information to the output.

The BIM feature is used to monitor the important set of jobs as a service and to proactively alert operations when it sees that some jobs in the critical path are failed or delayed. This helps a lot in maintaining our SLAs efficiently.

Control-M, with its huge integration capabilities, brought most of our scheduling activities under one roof. This adds to ease of use and support. To top that, the visibility it adds to the otherwise hidden information is very useful. In fact, invaluable.

Although we do not use tens of additional plugins available, we can see how they can be valuable to other companies.

BMC has now started concentrating more on APIs, which is a welcome move. This enables us to develop 'job as code'. This supports our efforts to adapt to a Continuous Integration/Continuous Delivery model. We hope that they make it one hundred percent compatible as early as possible.

Integration capabilities, plugins, support communities, visibility, MFT, Reports, APIs. As mentioned earlier, all these features mean that we don't need to use multiple solutions to do the task. It also makes things a lot easier that way.

MFT changed the way we manage our file transfers. On top of that, all of it is directly visible in the same GUI. All the statistics can be viewed at the click of a button. Although a bit flaky sometimes, it is very helpful.

Experts in the communities need a special mention here. There's a huge number of people who spend their valuable time helping each other, solving others problems. Although the actual BMC support can be slow in response sometimes, the expertise & the helpful nature of people in the BMC Community for Control-M more than make up for it.

MFT needs some more polishing. We ran into problems a few times & struggled to get them sorted in time. But, BMC gave their full support to us at such times.

APIs are not there one hundred percent yet, but BMC just adopted a monthly release mechanism for APIs. I can see that they are on it full time.

Inbuilt integration with Connect Direct could be helpful. A developer sandbox could be very helpful to try out new features or experience them.

Application Integrator can be helpful, although I don't see many templates being built by BMC experts. The hub that is available is mostly user-dependent.

It's stable ninety-nine percent of the time. Even the other one percent could be because of the funky underlying infrastructure/network setup.

Our job footprint is very low, so we never faced any scalability issues. From the documentation, it is my understanding that virtually, there is no limit to its scalability.

It can be slow at times, but you eventually come to an understanding that as long as you provide all of the information they 'might' need as early as possible, there are better chances that you get your answers 'sooner'.

I had used Cron scheduler for a short time, but it can be considered almost zero experience. My understanding is that BMC Control-M is years ahead in terms of usability & visibility.

The initial setup of this solution is very straight forward. BMCs AMIGO program is there to walk you through the process.

It gets a bit technical when you need to setup MFTs, but at the same time, it's not rocket science either.

We performed the deployment in-house with help from BMCs AMIGO program.

Pricing is a tricky area that I don't have much experience in. I can see it getting even trickier with more companies moving to a cloud-based infrastructure.

We did not evaluate other options before choosing this solution.

I like this solution, and my advice is to go for it :)

We do scheduling of tasks and jobs in Control-M.

The company has had the product for over 25 years.

The opportunity to automate work so you have an audit trail, especially with governmental requirements in a regulated industry, such as the airline industry. It's really important that we have that audit trail.

Because it's a tool which allows us to do scheduled work, it allows for notifications when jobs aren't running within that scheduled time frame. This improves the opportunity to meet SLAs.

We have all sorts of things which run through it, both on distributed and mainframe platforms. They all seem to run quite successfully. We're looking to add some additional work off of distributed platforms that will run with Oracle types of processing. But, we have a lot of work to come to the tool that we're not using it for yet.

It creates an audit trail for jobs that we run off of it.

With opportunity to run things through a repository, such as a scheduler, you have a better opportunity to ensure the information is where it needs to be when it needs to be there.

The company has been working with BMC on the MFT. There are still some things about MFT which don't work the way that we want with our needs. So, we would like to see that improved.

While the solution has affected the collaboration between our development and operations within our company, there is a need and opportunity to further that relationship with the use of this tool, so the enterprise uses it on all platforms. We will get there, but we are just not there yet.

For our shop, the tool is 99.9 percent reliable. We have very few instances of disruption with the tool.

We don't have any complaints about the usability. We like what it does. There are no issues with usability of the tool.

As we increase the number of tasks or jobs on the system, there are concerns about cost.

We previously used CA products.

We have seen ROI. Our in-house developed tool has been able to use the Control-M platform, making it easier for us to manage and monitor our file delivery processes.

Control-M saves us time.

Because we have been so pleased with this product, I would encourage others to look into this product with a view on what are their needs. Ask the right questions of either their sales rep or technical person from BMC to understand how this tool would work successfully for them, because it's been so successful for us.

Because we've had it for so long, and it's been such a stable product, some of our folks on the distributed side of things need to learn how to use Control-M effectively in regards to output when tasks or jobs fail. They need to give us smarter outputs, so we can resolve things more quickly.