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

AutoSys Workload Automation vs BMC AMI Ops comparison

Sponsored
 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 15, 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.6
Number of Reviews
42
Ranking in other categories
No ranking in other categories
AutoSys Workload Automation
Ranking in Workload Automation
4th
Average Rating
8.4
Reviews Sentiment
6.6
Number of Reviews
84
Ranking in other categories
No ranking in other categories
BMC AMI Ops
Ranking in Workload Automation
24th
Average Rating
9.6
Number of Reviews
2
Ranking in other categories
Mainframe Management (2nd)
 

Mindshare comparison

As of May 2026, in the Workload Automation category, the mindshare of JAMS is 3.0%, up from 1.9% compared to the previous year. The mindshare of AutoSys Workload Automation is 7.0%, down from 12.2% compared to the previous year. The mindshare of BMC AMI Ops is 2.1%, up from 0.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation Mindshare Distribution
ProductMindshare (%)
JAMS3.0%
AutoSys Workload Automation7.0%
BMC AMI Ops2.1%
Other87.9%
Workload Automation
 

Featured Reviews

LV
Principal Data Base And Infrastructure Engineer at a outsourcing company with 501-1,000 employees
Automation has replaced nightly monitoring and delivers reliable, unified job scheduling
We have really enjoyed working with JAMS in terms of notifications, alerts, and streamlining. There used to be a process with Automate, which is another product from Fortra, but even before that, the other division of the company that we were merging with had a tool that was built in-house called a file handler or file distributor. It was an in-house developed tool, but it was not as streamlined or as efficient as JAMS is. We literally had to have a dedicated nighttime person monitoring. Although we are 24/7, the divisions of the company that we were using JAMS for have been small scale. While we have automated it, we have streamlined it in such a way that notifications go out and alerts go out, but if there is anything, then we get paged and alerted, and if anything needs to happen at midnight, we can wake up. On the other hand, with the tool I mentioned, the file handler and distributor, we used to have a dedicated nighttime person that had to be sitting and monitoring it to see when a file arrived, whether it met the conditions, and then execute the next particular job. By using JAMS, we have gained a lot more efficiencies in terms of all of those to streamline it, and there is no necessary need for having an overnight engineer just keeping an eye on all of this.
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.
The service level and automated capacity manager functions allow us to control priorities, support SLA's and manage our 4HRA and reduce MLC for some software bills.
There currently is a WUI that allows an operator a single pane of glass to see how TM is performing to meet service policies within a JESMAS environment. This is a new feature and multiple individuals have expressed desire to not only see real time monitoring, but the ability to historically go back at least several hours or possibly an entire day to review history.

Quotes from Members

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

Pros

"The built-in triggers are great."
"The planning capabilities are most valuable."
"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."
"The most valuable aspect of JAMS is its robustness."
"One of the things I like the most, as a SQL DBA, is the fact that we can manipulate tables in the background. Also, the fact that you can have your own views and work with the product the way it fits best is a very helpful feature."
"JAMS has been a beneficial monitoring tool for our project in terms of being able to deliver data that is essential for users."
"Getting JAMS in place was a game changer for us back then."
"The dashboard is intuitive."
"In a billion dollar company, you want a scheduling product that is very robust, which can handle the magnitude of schedules that we run through it."
"The best features in AutoSys Workload Automation are its scalability and robustness; it can process a significant amount of jobs within a short period without delays when supported by powerful infrastructure and can communicate with endless agents and scan all 10,000 agent machines within minutes, updating agent statuses in the database quickly."
"The web UI is beneficial and the granular security policies allow us to cover all of our audit requirements."
"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."
"The most valuable feature of AutoSys Workload Automation is user-friendliness. If someone has some knowledge of the tool they can use it."
"It streamlines processing really well, so we're able to cut down on our processing times."
"The tool can probably handle way bigger stuff than what we are doing."
"We have great faith in the CA tech support website, and their responses to us every time we have a question, even if it's just a question on functionality, never mind it might be a problem that may come up, they respond to us very quickly; so we feel very, very secure with that."
"MainView has enabled me, in the past, to solve production problems faster, or even avoid them preemptively with warnings."
"The integration of IMS commands is very useful, because you do not have to switch to another tool to problem solve solutions."
"Enabled me to solve production problems faster or even avoid them preemptively with warnings."
"Batch smoothing our 4HRA and implementation of group capacity profiles has allowed us to run sub-capacity and lower our MLC."
 

Cons

"The solution is good, it's reliable. But sometimes the UI is not the most responsive I've ever used."
"All my machines at work are Macs. JAMS client is a Windows-based thing. It is all built on .NET, which makes perfect sense. However, that means in order for me to access it, I need to connect to a VPN, then log onto one of our Azure VMs in order to access the JAMS client. This is fine, but if for some reason I am unable to do so, it would be nice to be able to have a web-based JAMS client that has all the exact same functionality in it. There are probably a whole bunch of disadvantages that you would get with that as well, but that is definitely something that would make life easier in a few cases."
"The biggest area with room for improvement is the area that my organization benefits the most from using JAMS, and that is in custom execution methods. I happen to have a very good C# developer. Ever since we got JAMS, he has spent a lot of time talking to JAMS developers, researching the JAMS libraries, and creating custom execution methods. He's gotten very good at it. He is now able to create them and maintain them very easily, but that knowledge was hard-won knowledge. It was difficult to come by, and if I should ever lose this developer, then I would be hard-pressed to find anyone who could create JAMS custom execution methods quite as well as he can since there really isn't all that much help, such as documentation or information, available on how to create custom execution methods."
"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."
"Sometimes the UI is not the most responsive I've ever used. But because it does its job, I don't complain."
"For scalability, I would rate it as seven because when we have a huge volume, sometimes the tool is not so responsive."
"When looking at a folder in JAMS with many jobs, it would be good to have better information in the list display of what's inside those jobs. We get some information, but other important details are missing."
"JAMS handles exceptions fairly well but there are some areas where it might improve a little bit. It has to do with being able to automatically handle exceptions, out-of-the-box, rather than having to code them."
"There should be easier migrations from a different bus scheduler."
"The initial setup, what we had, was called 35 then we went to a 45 version. Now we went from the 45 to what's called R11, that was a nightmare."
"There is a slow response time by tech support. Unless, you say it's severity level one. That will give you a two hour timing window for them to call you. It doesn't really happen exactly in two hours, but they try."
"Because this product only computes processing days, it is hard when things need to be scheduled according to non-processing days."
"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.""
"We are not ready to go to the newest release (12.0)."
"We would like to see good improvement on the historical reporting capabilities."
"CA Workload Automation is not part of CA's strategic vision going forward."
"An expansion for distributed systems would be great, but probably not workable."
"More visualisation and support for mobile devices would be good."
"More visualisation and support for mobile devices would be good."
 

Pricing and Cost Advice

"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 pricing of JAMS has not been an issue for us, as it has allowed us to save time."
"Take advantage of its scalability. You can start small. The initial cost is very reasonable. Once you have started picking up the tool and adopting it, then you can scale up from there and buy more agents."
"The product is reasonably priced, and we don't have any add-ons."
"All licensing models are a little overpriced, but JAMS offers a good value, especially given their support response times and ability to handle unforeseen issues like the SFTP transfers. I hope to find more use cases to get a better bang for our buck."
"JAMS is relatively inexpensive, with additional costs only incurred for tags, other services, and optional support renewals."
"It's certainly a lot cheaper than Tivoli and Control-M. In comparison to them, you get a lot more bang for your buck. You get pretty much the whole functionality and more, in some cases, when compared to Control-M, but at a fraction of the price."
"For what it does, the product is priced very well."
"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."
"CA pricing has been a problem, and not looked upon favorably here at all."
"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."
"The return on investment would be very high because doing things manually without this product would be extremely expensive."
"We paid to use the solution monthly."
"I certainly think the pricing is worth the value."
"It is overpriced."
"If you already use other products from BMC, you might be able to get a package deal from BMC's sales department."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
893,244 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Construction Company
12%
Manufacturing Company
8%
Healthcare Company
6%
Financial Services Firm
39%
Manufacturing Company
9%
Retailer
5%
Insurance Company
5%
Financial Services Firm
25%
Manufacturing Company
8%
Government
7%
Outsourcing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise13
Large Enterprise19
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise5
Large Enterprise77
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for JAMS?
I believe the pricing and licensing were fair. I was not here when that process took place and do not know exactly, b...
What needs improvement with JAMS?
When it comes to improvements for JAMS, I think upgrading and migrating some of the current processes could benefit f...
What is your primary use case for JAMS?
Our main use case for JAMS is to automate our data pump backups for our PeopleSoft Oracle system, as well as run a my...
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 needs improvement with AutoSys Workload Automation?
There are areas of AutoSys Workload Automation that have room for improvement. They are implementing good enhancement...
What is the best network monitoring software for large enterprises?
I have worked from 1973 with all kind of systems in large enterprises across the world. And have experience with all ...
 

Also Known As

No data available
CA Workload Automation, CA Workload Automation AE
BMC MainView, BMC Automated Mainframe Intelligence, Ops Monitoring, Ops Automation for Batch ThruPut
 

Interactive Demo

Demo not available
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
Information Not Available
Find out what your peers are saying about AutoSys Workload Automation vs. BMC AMI Ops and other solutions. Updated: April 2026.
893,244 professionals have used our research since 2012.