Control-M Reviews

Because of security issues that we have, we are a private and public enterprise. Our main area is the lottery in Portugal. This is the most important business that we have. Also, because the money comes from the game, we need to invest it in social, health, and real estate areas.

For my current organization, it is a new tool. We are implementing the tool right now. We have a lot of impact jobs running every day and night, but in a skeletal matter. So, these jobs are running at one o'clock in the morning. With historical run jobs that we needed, we know it took six or seven hours to finish. Then, we have another cron job in another system at eight o'clock. With Control-M, we can reduce a lot of this time. Because when this job is finished, it will immediately start the job in another system. At this moment, we do this manually with an operator. Sometimes, they have errors because it is manual. It is not robots who do the job. Also, it takes a long time. We are losing time between jobs, if it is not automatic.

Our operator guys mostly use the web interface. As a client, we are more using the UI for the planning of the jobs. However, if we want only to do monitoring, then we only use the web interface. As we continue to work from home, there are a small number of operators who are still at our work. For security purposes, it is important to have the web interface in place because we don't like to install it on our clients because we don't have administration of the PCs. We cannot install on laptops without authorization. Access to Control-M only with a browser is really important and makes our job easier to do. We can access Control-M with a laptop, app, or mobile.

Before Control-M, we didn't have a centralized view and could not view what happened in the past to determine what will happen in the future. The Gantt view that we have in Control-M is like a project view. It is nice because we sometimes have some application maintenance that we need to do. So, in a single console, we can hold the jobs for the next hour or two. We can release that job when it is finished. This is a really nice feature that we didn't have before. It is something really simple, but we didn't previously have a console where we could say, "For the next two hours, what are the jobs that we will run? And, hold these jobs not to run." This is really important.

We use the Conversion Tool for audit purposes. We have had things working for a long time, but not documented. The Conversion Tool is nice because it helps us understand our jobs, whether they should be in Control-M or not. 

The most valuable feature for us is Managed File Transfer. We have a lot of file transfers in-house. Every FTP was being done by hand. Managed File Transfer is simply the best thing for us. This is the most used feature.

The credentials vault is really important. Before Control-M, every user's operator needed to know the username and password to access a system. With Control-M, we don't need to share passwords anymore. We write down the username and password one time, then we use it without knowing the password. 

The amount of integration that Control-M already has. We use the web services. We are using the SQL and Oracle integrations because we have a huge environment and a lot of applications in-house. Because we have integrations with all these tools, we don't need to give access to the operators. Now, we have everything in a single pane of glass. The operators can see all night what is happening, where, and if they need manual intervention.

One of our most used features is Control-M's library of plugins for orchestrating and monitoring work flows and data. We have a lot of different applications, plugins, and API automation, which are really important for us. We are migrating a tool from Apache, which is Java code. So, we can schedule the Java code with the API automation plugin that Control-M delivers for us. We are now starting to operate this way.

We use the Control-M Role-Based Administration feature. It is integrated with our Active Directory. We have groups in Active Directory, who are administrators and operators. Then, we map this role-base directly in Control-M. Role-Based Administration empowers us to decentralize product teams to manage their own application workflow orchestration environments with full autonomy. We divided this by environment: production, non-production, and demo environments. For each of these environments, we have different roles in Microsoft Active Directory. These roles are implemented by Control-M Role-Based Administration.

The use of Role-Based Administration eliminates the need to submit tickets or requests to the Control-M administrator. They don't open tickets and are autonomous when doing their job. From a security posture standpoint, it is important for us because we know that only the people who have credentials can access these environments, doing the job that they have to do.

We use Control-M Centralized Connection Profiles. We create the connections for the user and password. After that, we don't need to share passwords anymore, which is important for us.

We develop software. More frequently, we are working with microservices and APIs, using our integration tool, MuleSoft. While Control-M is really a good tool to integrate with other tools, it is important for them to continue improving their microservices and API.

I have been working with Control-M for more than 10 years. First, I was working in a consulting company, as a consultant, where we implemented Control-M. Now, in the last year, I have been a customer in a huge organization in Portugal. 

We can work with jobs that should run daily because of it. When we need to do an upgrade, it is really important for us not to have any downtime.

We are always afraid to install the latest version. However, with Control-M, it is really comfortable to move onto the latest version because of the stability. When I worked as a consultant, I never had any problems. Even when we had Control-M in two data centers, if one goes down, then we can run Control-M in another data center. Few software solutions have the stability of Control-M. 

We have different areas: real estate, games, social activities, and healthcare. The scalability for us is really important because we have different agents installed by business area. We don't mix it. Also, we have to always buy our VM servers per business area, so we can upscale how we want, which is really nice to have in Control-M. Critical jobs can run from different servers if something is not working.

BMC support is an eight out of 10. Everyone has centralized outsourcing for the first line of their service desk. They always ask some of their normal questions. After a while, once those guys know our workflow and understand that we already have some knowledge in Control-M, it is really fast to solve the problem.

We really needed a job scheduling tool. At the end of the day, we bought BMC Control-M. It is for a distributed environment where we have a lot of different working systems, operating systems, and applications. Control-M is the application and tool that meets our expectations.

The initial setup was straightforward. It is really easy to understand the architecture, and even install it. Based on some internal rules that we have in-house, Control-M fits well with our architecture.

It took a day to install and a week to implement. After one week, we had some jobs working and were able to get the users to see, control, and monitor the jobs. We had it deployed and working in less than a week for Windows, Linux, and HP-UX operating systems as well as VMS.

My principal difficulty implementing in-house was that people didn't understand what the job scheduling tool can do for us. It was long hours, and a lot of days, saying to our internal colleagues that this is the right tool. With this tool, we didn't need to have a lot of consoles anymore, i.e., working 24/7 to try and open every console to understand what is happening. We can have a single tool for all the jobs, applications, and operating systems. We can monitor and schedule all the jobs. They thought this is rocket science and doesn't exist. This solution has existed for a long time and is really important. 

The use of Centralized Connection Profiles has helped lower our total cost of ownership. Before BMC Control-M, we had different environments with the same users. We saw before that even the passwords for the different environments are the same. Before Control-M, we had passwords in emails and chats. Sometimes, the password would expire. With Control-M, we changed that. Every environment has an administrator who needs to write a password. We give them access to write the password directly into Control-M. The person configuring the job only needs to know who the user is, not the password.  With this functionality, the time that it takes has been reduced.

It reduces the duration for a lot of our jobs. We no longer have a window for maintenance applications at night.

This is an area where it is a little difficult to work with BMC. They want to do licenses by job, which is what we have. For example, the simplest is to license by job, but they can also license by nodes. While the licensing is simple to use, it might not be the correct licensing model for the customer. It is okay because we want to license by job, which is something measurable. At the end of the day, licensing by job is the most important.

We evaluated other vendors, like CA, but CA was bought by another company, and we have been a little afraid. Our organization always buys with a tender. Our tender had a lot of requirements on it and only Control-M could meet them all. It was a public tender, so we didn't really choose Control-M. We had a huge list of requirements that we really needed for job scaling. Only BMC could do it. IBM Tivoli tried to answer, but it didn't meet all our requirements.

Most tools have a huge GUI. You need to open five to seven windows to go to the parameters. Sometimes you don't have all the parameters in the GUI. With Control-M, it is three clicks and we have all the information that we need. We can see that in Control-M, we can see that all the perimeters are there for one job, like Managed File Transfer. It is very intuitive, and we can understand where to find the parameters to configure.

I think that every single company should have Control-M installed, because it is really important and useful for everyone.

I would rate this solution as a 10 out of 10.

A lot of the things we've done are just based on our needs, not so much because the product allows you to do it. Basically, I can do everything in Control-M. I mean, we've got plugins for Oracle, SQL, and Informatica, and I can go on and on and on. However, we don't use any of them as our developers prefer not to. A lot of what they do is they do the necessary connections through the batch files themselves.

It's used for our daily batch. It handles all the batch processes and a lot of our maintenance processes. I would say most of it is file movement of some sort. A lot of it is daily processing, to get it in. Our data warehouse runs through Control-M. The big impetus behind it, when we purchased it, was due to the fact that the auditors wanted a more robust system and something that they could audit. Control-M gives you everything you need for that.

It allows us to automate a lot of the jobs that used to run manually. Everything is automated. We can automate a lot of different processes using Control-M. You can know where it's at, and you can follow it, follow the job flow, from one job to the next, and whatnot, very easily. 

We used to run a lot of stuff in AT scheduler and Cron which really didn't meet the needs, especially for the auditors. We've taken that, and we've made the system where you know immediately if you got a problem with a job string. Our operations department will page it out overnight if we have a problem, and we take care of it. It's like any other system. If it allows you to do what you need to get done, it's the same every day, you know that you're going to get the same process. It drives the process.

Like most schedulers, you can bring jobs in many different ways. There are different ways to execute things. One of the things we had was when we were taken over. They were using a combination of the CA scheduler that they had, and they were also using SQL scheduler to do a lot of it. Prior to us converting our data warehouse system to Control-M, they were using the Informatica scheduler. None of this met any of the auditors. The auditors didn't like it as everything was spread out on different systems. They couldn't keep track of jobs. Everything's consolidated now. Everything's running off Control-M. You can follow everything through the entire process. We kick off all SQL jobs using Control-M. They were using SQL to launch just batch files, which had nothing to do with SQL - they were just scheduling it through SQL.

The capabilities of auditing have been great. 

The ease of use is one of its great aspects. It's very easy to use and very easy to pick up. 

It's got an excellent graphical interface. I haven't seen that in anything else that I've looked at, however, that said, I haven't looked at many lately. 

I know that in 20 years, I have had probably two problems where I've had to call the company to get immediate assistance from them, where we had a system down or something. Its performance is very reliable.

It integrates with other applications. You can use PowerShell, you can use Perl, you can use whatever. It doesn't really care. It's just running a process.

The product scales quite well.

Technical support is very helpful and available 24/7.

The stability is excellent.

I will say that at one time we used to run on Solaris and not Windows, however, we were taken over by a company that decided that everything had to be on Windows. We put this in when we were the previous company, and then we were more or less given to the current bank by the FDAC, during the 2009 banking crisis. At that point, they wanted us to implement their solution, which was rudimentary at best. It was a CA product that did not meet the needs. I could not convert what we had in Control-M, to run in that system at that time.

While they have a very good reporting facility, the reports that I'm asked to produce, a lot of times aren't necessarily what we need. They need to be better customized. I haven't been able to produce the right reports through their reportings facility. I was a Perl programmer and a C programmer at one time. Perl just worked right in there. A lot of our reports were written in Perl, which right now they don't like at all as Perl's not ideal for our company. 

I can't get to the database tables I want to get to. The database tables they allow me to get to aren't the ones I'm looking for, as, usually, I'm going right into the database, into the raw database, and pulling things out for the reporting I need. I can't do that through their reporting facility, Crystal Reports.

We've been using the solution for two decades or so. It's been about 20 years. We've used it for a long time. We started using it around 2000 or 2001.

We've had issues only twice in 20 years. It is very stable. I will say that they have improved it. Originally, when we put in a Windows version of it, we had problems with the database that they were using at the time, which was a Postgres database. Then, at one point, we decided to go to Solaris and run it on Solaris. We had it on Solaris for six years. In six years, I don't think we ever rebooted the server. It ran for six years without any hiccups, any problems. The Solaris system was rock solid. 

Now, the problems we run into, if we run into any problems, are Windows-based problems. Those Windows-based problems are, for example, if you don't reboot a server once a month, which, thank God we do, you can have issues. We reboot as we have to patch monthly now and we have to reboot it every month. However, we would see if we went two, three months on Windows, that we would start seeing some problems. Rebooting it took care of it.

That said, that's a Windows problem, not so much a Control-M issue, as we see problems on Windows servers that run for two or three months in any application.

Right now, we are running on their small database model. We, at one time, had about 2,500 jobs, and we were on a medium model then. Now, we're down to about 800 jobs a day. It's just a matter of the requirements we have. In terms of scalability, it scales up very nicely. It works very well. You can have multiple servers if you need multiple servers. Currently, we have one Control-M server and one EM server. We used to have two Control-M servers and one EM - EM being the enterprise manager, which is really what's running the system. The Control-M servers basically take care of the current runs, what's currently running on a system. Adding more jobs and adding more resources to it is not a problem.

It does high availability. We don't use the high availability due to the fact that we have another solution. We run everything in a virtual environment, and take regular snapshots if the system goes down. Should that happen, the snapshots are replicated from our production site to our DR site. We bring up the latest snapshot in the DR site if we lose the production site. It's up and running within minutes, literally. It's just a matter of going in and saying, "Bring these servers up." And they come up.

Currently, we've got three schedulers using the solution. They have more or less God rights, although they can't change user permissions. Those three schedulers can do anything with the jobs - delete, add, create, whatever. We have about 10 operators that have access to it as well. The operators have a somewhat reduced role from the schedulers. They can do a lot of it. They can bring in jobs, they can rerun jobs, they can kill jobs, however, there's a lot that they can't do. Then we have probably about 60 users that are developers, and they're basically read-only. They can see the jobs, they can see what happens. A lot of it has to do with corporate decisions on control. They didn't want the developers to be able to define jobs and items of that nature. They wanted the developers to define the job through a worksheet, and then the schedulers would actually implement the job. That's just a matter of policy, basically. They monitor their jobs that way. I'm trying to allow them to be able to at least bring in their jobs, for test - not for production - so that they can make it policy change here. If they could do that, it would greatly enhance their ability to get testing done. The downside to that is that you might have a developer that just keeps running the job over and over, and over, and over again, which I've seen happen too. Personally, I can do everything in test. I can't do anything in production at all, except view jobs. I have read-only on everything in production, except for the configuration part of it, to which I have full rights. I used to almost be a fourth scheduler at one time. At this point, there's no need. The limits of my job have been redefined several times.

Overall, the usage of the product in the company is very extensive. There's not a part of our daily businesses that's not reliant upon Control-M. If Control-M was done, the company would be at a standstill, literally.

That said, likely we won't increase usage. The company we just merged with, another organization and it's debatable as to how these things go. They have about 5,500 jobs. We used to have a lot of jobs like that, however, the business drives what we do. 

The technical support is probably the best I've ever worked with.

If I need support help from them, if we are down, they get back to me, if not immediately, within an hour. 24/7. And usually, we're up within an hour, after the first contact. They help greatly with planning for upgrades. I need to contact them here in the near future. They have a group called the AMIGO group, that does nothing but migrations and upgrades. I need to get with them to go over my plans for transitioning from the old servers to new servers. They will verify that what I'm doing is the right way to do it. If it's not, they will tell me how to do it, which is an excellent resource. 

They have a very large knowledge base. It's integrated with everything I've ever had to have it integrate with. Their support's been very good.

When I call BMC, I get an immediate response. I've had products that I've supported, that I've called companies and been on hold overnight. I've literally gone home for the night and left my phone on my desk, off the hook, on hold, and come in the next morning, and I'm still on hold, listening to the hold message due to the fact that the support hasn't answered yet.

We have recently merged with a company that uses Tidal, and of course, they want to hang on to theirs. We use Control-M. I've actually used several other scheduling products in the past, however, we've been on Control-M now for over 20 years.

I'm actually in the process of doing an implementation right now. I'm replacing our current production system. We're replacing EOS, actually, therefore, I'm doing a straight install of everything on the new servers. It is very straightforward. The install is not really difficult. It's fairly simple if you understand how databases work and whatnot. There's really no problem doing it.

In my case, I can bring up a Control-M server within hours. I only say that as I've done that, as we were not DR prepared back during Hurricane Sandy. I had to bring up a production version of it in Cleveland, in our DR site in Cleveland. Within 24 hours, we were up and running. Therefore, if you need it done fast, it can be done. It's just a matter of, are you willing to put in what you need to put in to do it.

It's a fairly easy install, really. I personally have never had any training on Control-M. Other people in my organization have had training. That said, I'm the one that put it in and I'm the one that read the manual. That's where I got all my information from, was from reading manuals and whatnot, and directly working with it.

I can't speak to what our support costs are. That's out of my realm at this point. At one point, I had an idea, however, I couldn't even tell you what that is anymore. I know that our licensing is based on jobs. We buy licenses based on the number of jobs. Currently, we have about 2,500 licenses. We used to run more jobs than we do right now. We did not get rid of those licenses. 

It's basically $100 a job, give or take.

They also don't charge us for items such as the plugins for MFTP, which we don't use, although we could. They wouldn't charge us for Oracle, SQL, or Informatica. It's a reporting product. 

There's no licensing for the server, there's no licensing for the EM server. All that stuff comes as part of the product. It's all-inclusive.

From what I've seen and heard from the other company about Tidal, that's where they're making their money from - the plugins. Whereas Control-M doesn't charge us. The plugins are basically free for us. I'm sure there is a charge for support every year. I have no idea what that is. I don't get down into that level.

I just tell them, "Yes, we need this" and then the purchasing staff takes care of the actual details.

At the time we were looking for a product, I looked at five or six different scheduling packages. By far, at that time, Control-M was leaps and bounds above all the rest of them.

We're customers and end-users.

We're using the latest version of the solution.

By far, BMC, from what I have seen, is the industry leader and they are the Cadillac of scheduling. I've worked with a lot of different scheduling systems over the years. When I first got into IT, years and years and years ago, as a JCL programmer, basically you had access to the scheduling system and you took care of the jobs. When jobs failed, you would do the restarts on them, do whatever fix needed to be done, and get them restarted, and get them to rerun. That was on a mainframe. 

I've used Cron, and I've worked with a number of different schedulers. In the Windows world, other than AT scheduler and Control-M, that's about all I've ever used. I did review five different products back when we put this in.

Having worked with so many products, and with this one for so long, I can advise that new uses should follow the installation instructions and notes. They're very simple, very straightforward. I would advise others to not get scared off by the price as, initially, the pricing seems rather steep, compared to some of the others. However, they all have their pricing quirks, and they're all making money in one way or another. The way they make their money is based on the way they license it. The per-job style actually works out very well.

I'd rate the product at a perfect ten out of ten. It has been one of the most stable products that I have supported, and I have supported a lot of different products. I've had fewer problems with it than I have with just about anything else I've supported. 

Control-M is used to schedule jobs and run them regularly. It helps to automate processes and reduce manual effort, minimizing the risk of errors and enhancing efficiency. Our clients use Control-M for various use cases, especially when there is a need for regular, automated job executions.

Control-M significantly reduces manual errors and enhances automation. It provides better scalability and more efficient data processing, making it a highly reliable solution for daily job operations.

Control-M can cross all platforms and offers integration for container and cloud solutions. This versatility is very helpful for my customers. The job scheduling capabilities are extremely convenient and easy to use, making Control-M a superior solution compared to others in the market.

I have no immediate ideas for improvements. I do not have any specific suggestions for additional features that should be included in the next release.

I have been using Control-M for about a year.

We do not encounter significant stability issues with Control-M. It runs jobs daily with stable performance.

Control-M is highly scalable. It offers complete functionality, making it an excellent choice for handling extensive operations.

Customer support is very responsive and efficient. If you open a case, it can usually be handled within one to two hours, especially for urgent issues. Their support is available in real-time and resolves issues promptly.

Positive

The initial setup of Control-M is easy and not difficult.

I always implement Control-M on-premises.

The pricing for Control-M is very expensive. It would be beneficial if the price could be reduced.

If your organization aims to reduce manual errors and enhance automation, Control-M is a suitable choice. It minimizes the risk of operational errors and missing processes, offering better scalability and automation.

I'd rate the solution nine out of ten.

We use the solution to transform essential files into an accessible format.

The solution's most valuable feature is its ability to reduce the number of jobs by passing various variables. It saves a lot of time for maintenance.

The solution's price could be better.

The solution is very stable.

I rate the solution's scalability as seven. Our team of around 30 monitoring executives uses the solution.

We contacted the support team for a failover issue. They fixed the error remotely.

The solution's deployment process took a day to complete.

We implement the solution with the help of a consulting company.

The solution is expensive.

I rate the solution as a seven.

I use BMC Control-M Managed File Transfer for file transfer management, which is its primary function.

What I like best about BMC Control-M Managed File Transfer is that it makes transfers more secure and faster. My experience with it is good.

I also like that it has personal dashboards.

I also found the functionality of BMC Control-M Managed File Transfer better, plus it has a recovery feature during failed file transfers.

An area for improvement in BMC Control-M Managed File Transfer is integration. It should be compatible with more solutions. BMC Control-M Managed File Transfer should have integrations with newer applications as well.

I have fifteen years of experience with BMC Control-M Managed File Transfer, and I'm still using it.

I didn't see any stability issues from BMC Control-M Managed File Transfer.

BMC Control-M Managed File Transfer has good scalability.

BMC Control-M Managed File Transfer has good technical support, as it has different engineers and consultants who resolve the issues.

My rating for BMC support is nine out of ten.

Positive

I chose BMC Control-M Managed File Transfer over the other solution because I know more about it, and it works better in terms of function.

Setting up BMC Control-M Managed File Transfer is easy, so it's a ten out of ten.

As BMC Control-M Managed File Transfer is a module, you install, implement, and run it in one day. It could take three weeks if you still need to install the solution that BMC Control-M Managed File Transfer is on.

You'll get ROI from BMC Control-M Managed File Transfer after using it a few times rather than once because the initial cost is high. With this module, you can reduce mistakes and not lose money, so you'll see ROI within one year or less from BMC Control-M Managed File Transfer.

BMC Control-M Managed File Transfer is relatively inexpensive. It has reasonable pricing. What you pay for is the task or job, and as it's a module, it's complimentary, so you save about twenty percent of the job cost. For example, if the job costs $100, BMC Control-M Managed File Transfer will cost $20.

Pricing-wise, the module is an eight out of ten.

I'm a software consultant and implemented BMC Control-M Managed File Transfer for different customers.

I've worked with older versions, from 6.4 to the latest version, 20.2, of BMC Control-M Managed File Transfer.

Deploying the module requires two engineers and one project manager who'll check the results of the project execution.

My advice to others looking into using BMC Control-M Managed File Transfer is that it's good to implement if you don't want to experience file transfer problems. The module has a tier that lets you transfer many files between different servers, so BMC Control-M Managed File Transfer is essential in file transfer and file management projects. You must make sure that you follow the steps on how to use the module.

Overall, BMC Control-M Managed File Transfer is a nine out of ten because it's easy to understand and use, plus it has a lot of benefits to customers.

Our primary use case for this solution is the data flow between our locations, between systems, and B2B data flow, which includes the data to the endpoints, the schemes and other lines. We deploy the solution on-premises.

For the IQ operation flow, we have to do a lot of planning with data resources and keeping the resources in front of the system. However, the solution has improved our organization by minimizing software dependency and managing data for our clients and regional schemes.

The file transfer, database, and integration features are the most valuable.

The solution can be improved by upgrading its features to compete with premium software in MFT. Additionally, Math and dollar features, along with product samples and VR functionalities, can be included in the next release.

We have been using the solution for approximately 15 years and are currently using version 20.200.

The solution is scalable. I rate it a nine out of ten.

The customer service and support team are very knowledgeable. I rate them a nine out of ten.

Positive

The initial setup is quite easy and depends on the speed of the background. So basically, if you're in the background, it's an eight out of ten.

We have seen a return on investment. The solution has saved us about 30% to 40% on additional investments in resources.

I rate the pricing a seven out of ten because there is room for improvement.

I rate the solution a nine out of ten. The solution is good, but its current functionalities can be upgraded. I recommend the solution to users considering it.

I am using BMC Control-M Managed File Transfer for transferring files.

The most valuable features of BMC Control-M Managed File Transfer are the ease of use and the ability to watch the files as they transfer called Watch File Transfer. There is a separate monitoring window that is useful.

Before we transfer files we have to make the connection profile first for MFT. If we did not have to do this and send the transfer files directly, that would be useful.

I have been using BMC Control-M Managed File Transfer for approximately three months.

I rate the stability of BMC Control-M Managed File Transfer a seven out of ten.

I rate the scalability of BMC Control-M Managed File Transfer a seven out of ten.

The communication from the support is very helpful.

I rate the support from BMC Control-M Managed File Transfer a nine out of ten.

Positive

The initial setup of BMC Control-M Managed File Transfer is easy, it took approximately one minute to complete.

I rate the initial setup of BMC Control-M Managed File Transfer a nine out of ten.

The implementation of the solution was done in-house.

I would recommend others follow the instructions given by the documentation and use it. That way, it is very simple to use.

I rate BMC Control-M Managed File Transfer a ten out of ten.

BMC Control-M Managed File Transfer has a scheduler and what they do is capture the steps based on the script, and then they put it into the Control-M job, or task. Any system that has the script behind it the solution can do it.

The GUI needs to be improved, they cannot provide a good GUI. That's the first improvement they should do.

I used BMC Control-M Managed File Transfer within the past 12 months.

BMC Control-M Managed File Transfer is highly stable. It is enterprise-grade software. Doing a job of 10,000 to 20,000 the solution is very stable.

The solution has very few bugs.

I have contacted the support from BMC Control-M Managed File Transfer. We have contacted them a lot, but only for technical aspects of the solution.

Their level two support is not very good. My team was able to solve a problem before they were able to. Level one support is us, the local support, in my country. Level two is usually from, India or another location because their R&D is in India. Level three, I don't know where the level three team is located, but the level three agents are the best. Level two support is not the best.

The license model is based on the number of tasks or jobs required. The price overall is expensive. In my country, we don't have any choice but to use them because no one can match their capability.

I rate BMC Control-M Managed File Transfer a nine out of ten.