No more typing reviews! Try our Samantha, our new voice AI agent.

AutoSys Workload Automation vs Control-M comparison

Sponsored
 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 13, 2026

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

JAMS
Sponsored
Ranking in Workload Automation
3rd
Average Rating
8.8
Reviews Sentiment
6.9
Number of Reviews
38
Ranking in other categories
No ranking in other categories
AutoSys Workload Automation
Ranking in Workload Automation
5th
Average Rating
8.4
Reviews Sentiment
6.6
Number of Reviews
84
Ranking in other categories
No ranking in other categories
Control-M
Ranking in Workload Automation
1st
Average Rating
8.8
Reviews Sentiment
6.8
Number of Reviews
193
Ranking in other categories
Process Automation (2nd), Managed File Transfer (MFT) (2nd), AI IT Support (1st)
 

Mindshare comparison

As of April 2026, in the Workload Automation category, the mindshare of JAMS is 2.8%, up from 1.8% compared to the previous year. The mindshare of AutoSys Workload Automation is 7.7%, down from 14.2% compared to the previous year. The mindshare of Control-M is 13.8%, down from 25.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation Mindshare Distribution
ProductMindshare (%)
Control-M13.8%
JAMS2.8%
AutoSys Workload Automation7.7%
Other75.7%
Workload Automation
 

Featured Reviews

reviewer2770605 - PeerSpot reviewer
Cloud Engineer at a financial services firm with 501-1,000 employees
Has streamlined complex job scheduling across scripting languages while reducing manual effort
JAMS could be improved with a web client that is accessible and as fast as a normal website, eliminating the need to RDP to the servers to access the JAMS client. A functionality running on the JAMS server to continuously check the JAMS agents would ensure they are working properly. If an agent is not responding, a feature to restart the service from the job server machine would be beneficial. The upgrade process, particularly when switching from V6 to V7, could be clearer in terms of documentation, ideally with screenshots showing exactly what needs to be done on each screen.
PK
Assistant VP at a financial services firm with 10,001+ employees
Experience significant automation with robust integration and user-friendly interfaces
There are areas of AutoSys Workload Automation that have room for improvement. They are implementing good enhancements in the R24 release. The web UI needs some improvement. Cloud integrations are limited to 25 or 30 configurable plugins and integrations to the cloud. They can improve in that area. They have separate tools, not AutoSys Workload Automation, such as Atomic and other SaaS-based solutions that can run inside the cloud. AutoSys Workload Automation can be configured in the cloud, but it requires a substantial number of VMs depending on the load. For on-premises deployment, it is a very good solution. They need to increase their footprint in the cloud and improve the web UI. They are making excellent progress in the R24 release.
RP
Batch Admin at NBC Universal
Brings data together from multiple platforms and optimizes cross-environment orchestration
The features of Control-M that I like the most include the ability to easily integrate or bring in different platforms into Control-M. For instance, AWS, mainframe, TWS, and something that's running on Autosys can all be brought into Control-M, converted to how Control-M runs it, and then the batch can be executed. This centralizes various applications in Control-M, which doesn't just have to handle batch processes, but also other tasks like reporting on required data. I find this functionality very useful and the setup is impressive, with more advancements yet to come. With Control-M, my company has achieved several measurable improvements since I started. The metrics indicate that the number of failures has dropped, and we have addressed the issue of excessive false alerts that I encountered when I joined. Previously, we received an overwhelming number of alerts daily, but now we manage to maintain that at a normalized level, perhaps around five to fifteen alerts, depending on running core batches and their setup.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"I find the historical tracking feature of JAMS invaluable for reviewing past events."
"The scheduling and execution of jobs are the most valuable features. The scheduling is important because if there is a task we want to execute at 4:00 AM, there's no way we will have someone who can manually run the job. In addition, we execute 100 to 200 jobs per day, and manual intervention is not an option."
"Our company is based on data. Everything we do is data-driven, so it has been very valuable having one place where we can process all of the data and do batch schedules with chunks of data."
"Getting JAMS in place was a game changer for us back then."
"JAMS has improved our productivity immensely because everything flows. I don't think we could operate at our current staffing levels without it."
"The user-friendly and adaptable scheduler allows us to manage various scheduling scenarios."
"The overall product is fantastic. I love it. It has been a fantastic, solid product. If I have one tiny bit of a problem with it, the support team gets in touch with me right away. I don't know if I've had another service that has been as fantastic as the JAMS support team."
"The feature or capability to import a job is most valuable. We can import an existing job from different platforms, and all the configurations get migrated as well without modifying the code, job schedule, etc."
"Now that we've got it and had it, it's very easy to use."
"Automation of patch process."
"The stability of AutoSys Workload Automation is good."
"I think it's been a good product for us, and I think others would find that to be true as well."
"We're able to monitor a complex workload, easily see where we're at in our batch flows, and take care of problems before they become bigger issues."
"We really like the product and its functions; it works, and we like its stability, scalability, and robustness."
"Autosys is one of the oldest products in the market, and it has been around for quite a long time, close to 20 to 25 years."
"To me, what's most valuable in AutoSys Workload Automation is its robustness and quickness. The tool can trigger jobs within a few milliseconds, and it can handle large volumes of jobs."
"Control-M has improved our visibility and streamlining, giving us better clarity into data flows so we can resolve issues faster and provide audit answers quickly and with confidence instead of reverse engineering convoluted pipelines."
"Control-M is the easiest tool available because we can accomplish what we want."
"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."
"We used Control-M's Python Client and cloud data service integrations with AWS and, as a feature, it was very customizable. It gave us a lot of flexibility for customizing whatever data maneuver we wanted to do within a pipeline."
"Control-M acts as a one-stop shop to check the status of all jobs."
"The File Transfer component is quite valuable. The integration with products such as Informatica and SAP are very valuable to us as well. Rather than having to build our own interface into those products, we can use the ones that come out of the box. The integration with databases is valuable as well. We use database jobs quite a bit."
"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."
"It does provide a lot of flexibility, especially with the application and integration component that they have."
 

Cons

"Sometimes the UI is not the most responsive I've ever used. But because it does its job, I don't complain."
"It is important to receive notifications if a charged job fails and SQL is halted. JAMS does not provide halted notifications by default, which is a critical feature that needs to be added."
"I would like a simple web interface that I could give to my team to go in and kill jobs or see why jobs died so that we don't have to drill down deeper into the application and know everything about it. It would be good to have a really clean web engine that would say here are the jobs running. We can then click to see the time running and whether any of them fails and other similar things. I know they have one, but it's not very simplistic."
"Fortra is getting much better with documentation and examples, but there is still room for improvement."
"The UI could be better. There were some things that were not quite intuitive, such as the search tool. When we tried to search for jobs, we had to clear the entire search and then go in and enter the new search query. That's something that wasn't intuitive for a new user."
"If around 5,000 or more jobs run at a time, JAMS slows down, and we have to wait around five to 10 minutes or restart JAMS scheduler services."
"There could be a better simulation for banning the termination. You have to simulate every one of the processes in order to have an idea for better planning. This kind of simulation is broken and needs improvement."
"There could be a better simulation for banning the termination. You have to simulate every one of the processes in order to have an idea for better planning. This kind of simulation is broken and needs improvement."
"The scalability could be improved upon."
"We had a few issues, however, the issues were more on the infrastructure rather than with the application itself."
"It would be helpful to be able to monitor and manage workload windows so we could minimize downstream applications. This would allow us easier access to the applications."
"This product needs to improve its graphical user interface."
"In terms of what should be in the next release, I want integration and AI and so on. I'd like easy reporting where you can compare information, for example, "that job normally takes three minutes and last time it took six minutes or 10 minutes." Then you can get the information to the engineer of which job is taking more time than normal - understanding strange behavior compared to the baseline."
"AutoSys Workload Automation does not perform performance tuning, monitoring, or management."
"Reduce the number of operational files. This would make the job of a system programmer supporting ESP easier."
"The way that it was brought to us, in our initial setup, we had a lot of initial questions and they replied, "Well, set it up the way you want it." It was kind of confusing from an end-user support aspect, asking them what are the best practices."
"They really need to work on improving the web interface, as there are still a lot of bugs."
"Its architecture is old. AutoSys gives more flexibility."
"Control-M reporting is a bit of a pain point right now. Control-M doesn't have robust reporting. I would like to see better reporting options. I would like to be able to pull charts or statistics that look nicer. Right now, we can pull some data, but it is kind of choppy. It would be nicer to have enterprise-level reporting that you can present to managers."
"The process to apply patches and upgrades is cumbersome. It feels like there could be a simpler or more streamlined way to apply patches."
"A lot of businesses are using ServiceNow, which is another tool. I would like there to be some integration with ServiceNow or other third-party tools as well as have easily available integrations."
"Integration with some applications and platforms is complex and requires development."
"The structure between the Control-M/Server and Control-M/Agent could possibly be improved."
"The area that has room for improvement in Control-M is a better dashboard. For example, sometimes we have up to 100 Control-M jobs, and there is no dashboard to know how many jobs are in progress, completed, or waiting for files."
 

Pricing and Cost Advice

"JAMS is relatively inexpensive, with additional costs only incurred for tags, other services, and optional support renewals."
"For what it does, the product is priced very well."
"Definitely check how many single processes you want to run and count them as jobs. That is how you would work out your pricing on JAMS. For example, if you're running a number of commands and you can put them all into one script and run that script, you can count that as one job."
"The licensing model for JAMS is straightforward and based on the number of agents, not the number of jobs you run. It's cheap and fairly simple."
"The pricing of JAMS has not been an issue for us, as it has allowed us to save time."
"The product is reasonably priced, and we don't have any add-ons."
"I haven't been involved in the financial side for several years, but we buy one host and unlimited agents, and we get a reasonable price for that. We're happy with the amount we pay and the scalability it provides."
"There are no additional costs other than the license for Fortra's JAMS which is affordable."
"The return on investment would be very high because doing things manually without this product would be extremely expensive."
"I don't have information on the exact licensing cost of AutoSys Workload Automation because that's managed by the tools and financing teams. For agents, it's close to $4,00, but for the server setup, it's usually a one-time license initially, and it's AMC which is paid every year and comes close to $8,000 to $10,000."
"Validate how many agents you need beforehand."
"CA pricing has been a problem, and not looked upon favorably here at all."
"The pricing needs to be improved. Some of my client's complained that it was too expensive."
"We paid to use the solution monthly."
"The price of this solution is reasonable and there is an annual license required."
"People need to pay attention to how they use their ESP agents on the distributed platform. That's where some of the cost comes in, based on how many you need or how many you use."
"The annual licensing within BMC Control-M is on a per task basis. Three- and five-year contracts are also offered. The customer usually buys a bundle of tasks, e.g., 5,000 tasks, then my team configures Control-M for their usage."
"BMC's price is based on the number of jobs."
"Its pricing is a little bit high. They could provide an enterprise-level license for an unlimited number of jobs. Currently, it is based on the number of jobs, and if you exceed the number of jobs, there are charges. For example, if your license is for 3,000 jobs per day, but you run 3,050 jobs, you will have to pay for the extra 50 jobs. They charge $120 per job. So, it is too costly."
"This is now from my previous years as support for banks and big companies. If it's not enterprise scale, I find that it's too expensive for smaller companies. You really have to be quite big and need to have a dedicated support staff to run it, then you'll be fine. What we've seen at smaller companies, it's too expensive because they want to automate everything. Now, stuff that can literally run once a day for the rest of their lives is costing them $3 a job a day. It becomes too expensive, eventually. They are not seeing the return on investment because it's not business critical. Nobody is going to die or they're going to lose money if that job didn't run exactly at 11 minutes past 4:00. It's definitely for bigger enterprise companies, especially banks or healthcare providers. We have had an instance where Control-M was unavailable due to external factors for 20 minutes and there was a loss of almost a million euros because the solution involved logistics."
"This is an expensive product compared to other solutions, although I think that it is a good one. We are in a good position with licensing, as we can run 10,000 jobs."
"The pricing is reasonable. It's not an exorbitant amount. The licensing is pretty reasonable for the number of jobs that we run."
"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."
"They are expensive. If we were a small company, it would be complicated because we have to have strong sales and operations to be able to afford a tool of this level. Being a large company, the cost-benefit is covered, but it is not within the level of cheap solutions."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
885,444 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
14%
Financial Services Firm
13%
Manufacturing Company
8%
Computer Software Company
8%
Financial Services Firm
40%
Manufacturing Company
9%
Insurance Company
5%
Retailer
5%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business12
Midsize Enterprise8
Large Enterprise19
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise5
Large Enterprise77
By reviewers
Company SizeCount
Small Business38
Midsize Enterprise25
Large Enterprise152
 

Questions from the Community

What do you like most about JAMS?
I find the historical tracking feature of JAMS invaluable for reviewing past events.
What is your experience regarding pricing and costs for JAMS?
My thoughts on the pricing of JAMS are that I won't say it is cheap, but it is cost-efficient, and that should be acc...
What needs improvement with JAMS?
An area that has room for improvement is related to the AWS RDS and database part, where they said that is in progres...
How does Control-M compare with AutoSys Workload Automation?
Control-M acts as a single, centralized interface for monitoring and managing all batch processes, which is helpful b...
What do you like most about AutoSys Workload Automation?
The most valuable aspects of AutoSys Workload Automation are its performance, scalability, and ease of getting starte...
What do you like most about Control-M?
First of all, the shift from manual to automation has been valuable. We have a tool that can automate.
What is your experience regarding pricing and costs for Control-M?
From what I know about pricing, I would probably put Control-M in the expensive category, but you do pay for what you...
What needs improvement with Control-M?
We are not on the latest version of Control-M; we currently have version 20 and 21.
 

Also Known As

No data available
CA Workload Automation, CA Workload Automation AE
Control M, BMC Control-M Managed File Transfer, BMC Australia CTM
 

Interactive Demo

Demo not available
 

Overview

 

Sample Customers

Teradata, Arconic, General Dynamics, Yum!, CVS Health, Comcast, Ghiradelli, & Boston’s Children’s Hospital
Gaumont, Mercantil do Brasil, CCEE, Hanwha Life
The Bank of East Asia, LINE Bank Taiwan, Coop, Air Europa, Carrefour, Itau Unibanco, Snam, Embraer, ANZ Bank, EDP, Dominio's, Tampa General Hospital, W&W Informatik GmbH, Veterans General, Up Sí Vale, Sky Italia, REWE digital GmbH, Raymond James, Railinc, Navistar, Management Science Associates, Colruyt, CARFAX, Banpara, Aspiag Service, Amadeus, AG Insurance, ING Bank Slaski
Find out what your peers are saying about AutoSys Workload Automation vs. Control-M and other solutions. Updated: March 2026.
885,444 professionals have used our research since 2012.