Try our new research platform with insights from 80,000+ expert users

AutoSys Workload Automation vs JAMS comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jun 8, 2025

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

AutoSys Workload Automation
Ranking in Workload Automation
7th
Average Rating
8.4
Reviews Sentiment
7.4
Number of Reviews
82
Ranking in other categories
No ranking in other categories
JAMS
Ranking in Workload Automation
5th
Average Rating
8.8
Reviews Sentiment
7.6
Number of Reviews
35
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of July 2025, in the Workload Automation category, the mindshare of AutoSys Workload Automation is 11.0%, down from 17.5% compared to the previous year. The mindshare of JAMS is 2.0%, up from 1.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation
 

Featured Reviews

Antony Askew - PeerSpot reviewer
Helps us manage complex workloads, reduce our workload failure rates, and save us time
The visibility and control features are somewhat limited. This is a recognized weakness, but thee vendor is currently revamping the user interface to address it. While the current UI is a bit outdated, it's undergoing improvement. AutoSys Workload Automation has some areas for improvement, particularly in housekeeping and product maintenance. These tasks are currently quite manual and labor-intensive for our team. Additionally, the reporting and forecasting functionalities could be more robust. One area for improvement with AutoSys Workload Automation is that it comprises several distinct tools configured to work together. This necessitates familiarity with multiple tools for effective solution management. Consequently, it can sometimes lack a sense of cohesiveness as a unified solution.
Patrick Norton - PeerSpot reviewer
Support has been among the most helpful and knowledgeable we've ever worked with but performance monitoring needs improvement
The monitoring of the JAMS product and its performance is an area of concern for me. I also need better tools to adopt version seven. Another area for improvement would be the addition of source control for jobs internally, as this feature would solve several problems for me. JAMS has some quirks. It has a bit of a learning curve. Some exceptions are not intuitive, such as when a job is terminated due to exceeding its defined runaway time limit. This generates a misleading exception message that is difficult for new users to understand and requires experience to interpret correctly. Stalled jobs present a unique challenge, particularly when pushing a system like JAMS version six to its limits. While rare, these instances occur when jobs become unresponsive despite appearing in API queries but not in the monitoring console. Although workarounds exist, they highlight the need for improved native monitoring capabilities within JAMS. Currently, the system assumes flawless operation, necessitating supplemental monitoring tools to detect issues like excessive pending or stalled jobs, ensuring timely intervention by our teams.

Quotes from Members

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

Pros

"It has helped to simplify cross-dependency between MVS and Open systems jobs."
"It's very easy to work with. The learning curve is not that steep."
"I find that it provides better agility in regards to job execution features."
"The most valuable feature of this solution is the functions are easy to use."
"The solution has been stable."
"The ability to create calendars, calendering for batch jobs to run on a scheduled frequency."
"​It scales very well. We can add jobs and remove jobs. We do not have problems maintaining the product across multiple environments and multiple servers.​"
"Inherit Dependencies feature reduces scheduling errors for holiday processing."
"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 built-in triggers are great."
"The most valuable feature is the easily accessible data in the database because we run a lot of SQL scripting against the database."
"I like how you can add new execution methods on the fly. It isn't overly complex to add Python script support to an execution method in the JAMS system. The scheduling is excellent. You can schedule a maintenance window and take that resource unit out of everything. It halts all of the jobs."
"The most valuable feature for us is that it's DR-ready. With respect to disaster recovery, it has the built-in capability for failover to our DR site. If all of the required ports are open, it can be done seamlessly."
"The fact that we no longer need to use Excel spreadsheets is huge. Before JAMS, every group was keeping track of their own batch jobs. Nobody really knew what the other jobs were. So, if jobs failed, other groups wouldn't necessarily know. With JAMS, everything is done through a single scheduler. You can choose who to notify."
"It makes everything that we want to do so much easier. We have had a number of instances in the past where we have had developers who have been working on a project, and even though we have had JAMS for all these years, they will create some SQL Server Agent job, or something like that, to run a task. When it is in code review and development is complete, the question always comes around, "Can JAMS do this?" The answer has always been, "Yes." Pretty much anything we have ever developed could be run by JAMS."
"The alerting in it is really targeted... you can set specific alerting so that if jobs in a given folder fail, certain people are alerted. You can also set security at the folder level, so that only people in those areas can go set them. That means that the alerting and security can be set at a very granular level."
 

Cons

"We see improvement possibilities in the processing provision of predefined evaluations or individual objects, or in the Self Service portal, which can be used by any user to monitor objects or start objects."
"SQL server clustering is not supported."
"An area for improvement in AutoSys Workload Automation is that it lacks advanced features or advanced built-in functionalities found in competitors, for example, an advanced workflow feature. Even the handling or notification from AutoSys Workload Automation isn't the best in the industry. Other products have very good workflow-related functionalities such as ActiveBatch that's missing in AutoSys Workload Automation, so I wish the tool had those features."
"There is a difference between a web interface and the thick client interface. We particularly like a thick client interface, and it has gone away."
"Because this product only computes processing days, it is hard when things need to be scheduled according to non-processing days."
"I would like to see the Service Orchestrator, a B2B product, and maybe a process audit."
"We have to escalate through channels to get to somebody who knows what's going on. It takes time that we do not necessarily have.​"
"AutoSys Workload Automation could improve in the Linux environment. The previous versions of the AutoSys Workload Automation let you take the profile of the user that you were using to run the tasks that you're going to automate, but in the latest versions, you can't do that, you need to make more definitions and it's a little bit difficult. It was easier in the previous versions."
"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."
"The error messages from JAMS often need clarification, hindering our ability to resolve issues swiftly."
"I want JAMS to implement a global search function."
"I would like to see the ability to interface with Microsoft group-managed service accounts, but they're still in the research phase. They need to ensure everything's legit and safe. The report designer and dashboards could also be improved. We're running 7.3, so I don't know if they have updated the reporting in 7.5, but I think the reports and dashboards could be better."
"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."
"JAMS notifications for hung jobs could be improved."
"Sometimes the UI is not the most responsive I've ever used. But because it does its job, I don't complain."
"Improvements could be made in the service desk's knowledge and communication skills among engineers to better address customer needs and ensure issues are fully resolved."
 

Pricing and Cost Advice

"We paid to use the solution monthly."
"The price of this solution is reasonable and there is an annual license required."
"The pricing needs to be improved. Some of my client's complained that it was too expensive."
"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."
"It is overpriced."
"There is an annual license to use AutoSys Workload Automation."
"CA pricing has been a problem, and not looked upon favorably here at all."
"Validate how many agents you need beforehand."
"JAMS is priced competitively compared to similar solutions and offers flexible licensing options to cater to user needs."
"This is a good product at a fair price."
"The product is reasonably priced, and we don't have any add-ons."
"JAMS is relatively inexpensive, with additional costs only incurred for tags, other services, and optional support renewals."
"In the end, you'll find that it's really worth the price. There is some sticker shock, but it's worth every dime."
"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 product is reasonably priced, and we don't have any add-ons."
"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."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
860,825 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
47%
Manufacturing Company
9%
Computer Software Company
6%
Insurance Company
5%
Computer Software Company
18%
Financial Services Firm
14%
Healthcare Company
7%
Manufacturing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

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 because nothing gets left unattended since it is all visible in one place, and th...
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 started for new users.
What is your experience regarding pricing and costs for AutoSys Workload Automation?
The solution is costly. The pricing is based on the number of users, which for me, translates to approximately $120,000 to $130,000 for a license period of two to three years.
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?
They recently switched to subscription-based pricing, which increased. The price is fair considering the functionality and importance of the tool, although the increase did unsettle our management.
What needs improvement with JAMS?
A major improvement would be the integration of AI to help us accomplish various tasks. AI could assist in simplifying operations and could potentially enhance the tool's capabilities.
 

Also Known As

CA Workload Automation, CA Workload Automation AE
No data available
 

Interactive Demo

Demo not available
 

Overview

 

Sample Customers

Gaumont, Mercantil do Brasil, CCEE, Hanwha Life
Teradata, Arconic, General Dynamics, Yum!, CVS Health, Comcast, Ghiradelli, & Boston’s Children’s Hospital
Find out what your peers are saying about AutoSys Workload Automation vs. JAMS and other solutions. Updated: June 2025.
860,825 professionals have used our research since 2012.