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

IBM Workload Automation vs JAMS comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 4, 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

IBM Workload Automation
Ranking in Workload Automation
12th
Average Rating
8.0
Reviews Sentiment
7.1
Number of Reviews
32
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
34
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of April 2025, in the Workload Automation category, the mindshare of IBM Workload Automation is 7.2%, down from 8.4% compared to the previous year. The mindshare of JAMS is 1.7%, up from 1.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation
 

Featured Reviews

Ilhami Arikan - PeerSpot reviewer
With an easy setup phase in place, agent-based installation can be done in minutes
Sometimes we have issues with the solution's stability. So, stability can be improved. Reporting and visibility of the solution need improvement. These days, we need more visibility. We need to access the logs and databases easily. You need to keep track of the running number of logs, like which ones are executed, completed, etc. So if there would be a good reporting dashboard, then it would be good. There's room for improvement in the solution since it is a challenging thing when we want to use the solution's technology with our new technologies. For example, if we need to use TWS on our OpenShift platform, the solution's API is not capable enough. So the product itself needs to be aligned with new technologies.
Rob Grafrath - PeerSpot reviewer
We can scale up our organization's scheduling and automation without having to add staff to the department
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 was hard-won knowledge. If I ever lose this developer, I would be hard-pressed to find anyone who could create JAMS custom execution methods 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 really think that they could benefit greatly by being much more transparent about C# development, maybe by making a JAMS cookbook or a developer portal where they could throw ideas at each other. One of my complaints with the marketing around JAMS is that it says things like, "It integrates with Teams". They talk about integrating with a lot of things, but marketing doesn't tell you that they are talking about JAMS running PowerShell jobs. Since PowerShell can automate things like SharePoint and Teams, that is how marketing gets away with saying it has so many integrations. JAMS doesn't have as many built-in integrations as they advertise. I think they should build more of them, and improve on the ones they have built.

Quotes from Members

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

Pros

"Jobs can be triggered in multiple nodes."
"The initial setup is easy."
"The most important feature is the creation of folders. It's a really great feature because you can organize the process with naming conventions."
"Jobs can be triggered in multiple nodes."
"The project we worked on involved the running of nearly 24,000 job instances in a single day, so I would say that the solution is stable."
"The technical support is great, the product is easy-to-use, and it is stable."
"It offers features like MDM and a Windows workstation, although there are some technical dependencies. It is more user-friendly and also includes failover and failback capabilities. While both systems offer high availability, Control-M's high availability is superior to AWS's."
"The support from Cisco is very good. I was with them as a company for 40 years"
"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."
"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."
"JAMS is easier to use and cheaper than our previous solution. The installation is more straightforward, and JAMS has a graphical user interface, so it's more accessible."
"Fortra's JAMS helped us centralize job management across our platforms and applications. This is critical because we schedule tasks across multiple applications and operating systems, using triggers and start dates to coordinate their execution."
"We looked at other companies, like VisualCron, that were cheaper, but one of the main sticking points was the fact that they wouldn't have provided a central location for us to monitor across all servers. That was one of the biggest selling points of JAMS."
"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."
"While I appreciate the other features, the agent stands out for its ease of installation and configuration for JAMS monitoring."
"Being able to create a series of chained jobs, which are basically linked jobs is valuable."
 

Cons

"Slow down on the releases a bit. I fully understand that IWA functionality is increasing at an amazing rate, but trying to keep up with the upgrades is rough."
"It should support other schedulers that aren't IBM products."
"It would be helpful to have a mobile app that could be used to follow the job schedule."
"The solution's installation could be improved because the customers have to do it all the time."
"There should be more custom documentation, specifically around Java APIs. There should also be more training. In terms of features, we are currently using only 50% of its features. We don't use all features that are available, but there is always room for improvement in all of the tools."
"Scalability-wise, it can be a little bit challenging."
"It is missing some features and can improve in areas where the competition is somewhat better like linking job dependencies."
"IBM needs to move away from its native terminology and adopt a more cloud-centric approach."
"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."
"The error messages from JAMS often need clarification, hindering our ability to resolve issues swiftly."
"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."
"With no programming experience, I find JAMS code-driven automation challenging due to the required PowerShell scripting."
"JAMS lacks source control features. Our previous solution had job control language, but JAMS doesn't. When migrating between versions, JAMS doesn't migrate all the data, like job change history, etc. Also, the scheduler doesn't have a way to make jobs invisible, so you can temporarily turn a job off if you decide not to run it today."
"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 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."
 

Pricing and Cost Advice

"To my knowledge, IWA is the only WLA product that will provide "parallel tracking" capability to assist in upgrading from one platform to IWA."
"We transitioned from a server license to per job license, and that saved us a lot money."
"It is about one-third of the cost of a controller."
"The solution is a little bit expensive."
"The solution's pricing is affordable."
"Pricing depends on the number of agents that you install."
"The contract is with the customer with whom we are working, so IBM is not directly involved in this."
"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."
"This is a good product at a fair price."
"In the end, you'll find that it's really worth the price. There is some sticker shock, but it's worth every dime."
"It was $10,000 for the first year. Then, there is a maintenance cost for licensing every year that we get billed $5,000 for every year."
"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."
"It's expensive, to be honest, but it does the job."
"JAMS is priced competitively compared to similar solutions and offers flexible licensing options to cater to user needs."
"The pricing is reasonable."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
845,406 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
32%
Computer Software Company
9%
Manufacturing Company
8%
Retailer
8%
Financial Services Firm
16%
Computer Software Company
16%
Healthcare Company
9%
Manufacturing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What needs improvement with IBM Workload Automation?
IBM needs to move away from its native terminology and adopt a more cloud-centric approach. For example, IBM still refers to machines as 'workstations,' whereas other systems, like Control-M, use m...
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?
Fortra's JAMS pricing structure has deteriorated significantly since its acquisition by Fortra. Previously, both Help Systems and MVP offered more favorable pricing and licensing terms. However, Fo...
What needs improvement with JAMS?
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 co...
 

Also Known As

IBM Tivoli Workload Scheduler, IBM TWS
No data available
 

Overview

 

Sample Customers

Standard Life Group, Banca Popolare di Milano, A*STAR, ArcelorMittal Gent
Teradata, Arconic, General Dynamics, Yum!, CVS Health, Comcast, Ghiradelli, & Boston’s Children’s Hospital
Find out what your peers are saying about IBM Workload Automation vs. JAMS and other solutions. Updated: March 2025.
845,406 professionals have used our research since 2012.