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

Flux vs IBM Workload Automation comparison

Sponsored
 

Comparison Buyer's Guide

Executive Summary

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.4
Number of Reviews
45
Ranking in other categories
No ranking in other categories
Flux
Ranking in Workload Automation
28th
Average Rating
10.0
Reviews Sentiment
6.5
Number of Reviews
2
Ranking in other categories
Managed File Transfer (MFT) (22nd)
IBM Workload Automation
Ranking in Workload Automation
12th
Average Rating
8.0
Reviews Sentiment
7.0
Number of Reviews
33
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of August 2026, in the Workload Automation category, the mindshare of JAMS is 3.1%, up from 1.9% compared to the previous year. The mindshare of Flux is 1.9%, up from 0.2% compared to the previous year. The mindshare of IBM Workload Automation is 4.1%, down from 6.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Workload Automation Mindshare Distribution
ProductMindshare (%)
JAMS3.1%
IBM Workload Automation4.1%
Flux1.9%
Other90.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.
it_user4080 - PeerSpot reviewer
Developer at a comms service provider with 1,001-5,000 employees
Lightweight and extensible with great support staff
* Lightweight * Uses java standards * Can run in j2se or j2ee environments * Can run as embedded or standalone * Works with multiple db or in-memory * Great support staff * Extensible * Cluster(able) * Can integrate and be a major player in any SOA environmentFlux has made excellent design choices the benefits of which can be passed down to customers in terms of price and capability. I don't see any IT vendor rival this.
reviewer2701716 - PeerSpot reviewer
Technical Lead at a financial services firm with 1,001-5,000 employees
Dynamic workload balancing facilitates efficient job scheduling and ensures continuity with a master-slave setup
One valuable feature of IBM Workload Automation is the ability to combine different applications and platforms to organize jobs together, creating dependencies. It's akin to an orchestra. Another feature is dynamic workload balancing, which I find enhances efficiency by automating job setup to run daily. Moreover, having a backup setup allows for immediate recovery if the master setup fails.

Quotes from Members

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

Pros

"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 user-friendly and adaptable scheduler allows us to manage various scheduling scenarios."
"The code-driven automation for more complex scheduling requirements frees up time because it's really easy to use... It's almost like a stand-alone software that we can't live without."
"I find the historical tracking feature of JAMS invaluable for reviewing past events."
"JAMS offers diverse scheduling capabilities for any kind of job, including Linux, PowerShell scripts, and SQL, enabling automation of jobs, which has proven beautiful after three years of usage."
"The product is easy to use."
"JAMS has positively impacted our organization by saving us time, reducing errors, and improving workflows."
"JAMS has been a beneficial monitoring tool for our project in terms of being able to deliver data that is essential for users."
"Flux has made excellent design choices the benefits of which can be passed down to customers in terms of price and capability."
"Excellent customer support"
"Depending on that it may be interesting to use Tivoli because it is a good tool."
"Jobs can be triggered in multiple nodes."
"The whole product is valuable because it is a tool for batch automation."
"IBM Workload Automation provides good performance and monitoring."
"With FTA (Fault Tolerant Agent) on remote servers, you have Agents to run jobs."
"The most important feature is the creation of folders. It's a really great feature because you can organize the process with naming conventions."
"Provides a robust, full spectrum enterprise-wide WLA platform."
"I would recommend other users to definitely consider TWS, as it has proven to be a powerful tool in our environment so far."
 

Cons

"The JAMS automation code isn't so clean."
"The ACL or access permission area needs to be improved. When it comes to defining and providing security permissions, it's a bit confusing if you are new to JAMS. JAMS needs to improve the features for security access or permissions."
"Fortra is getting much better with documentation and examples, but there is still room for improvement."
"Right now there's not much of an Azure integration with JAMS at the moment directly because we run separate pipelines."
"The client is horrible. Every time JAMS puts out a survey on what they can improve, I always say, "The client: When you are setting up jobs, it is quite horrible." The response has been, "Well, we are just using the Windows foundation," and I am like, "Why isn't it only your product?" We can get around it now that we know its quirks, but it is not the most user-friendly of tools out there. The UI is completely unintuitive. We had to go and open up a support ticket with JAMS just to get something back. It is not user-friendly at all."
"All my machines at work are Macs. JAMS client is a Windows-based thing."
"For the most part, JAMS is very stable. Occasionally, if you leave multiple windows open over a period of time, it is necessary to end that task and restart."
"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."
"It would be nice to have more file transform capabilities for transforming xml and csv documents."
"Need a better way to track a particular work item through multiple, independent workflows."
"We are using an outdated version. We had issues with the file dependencies."
"The configuration of IBM Workload Automation has some challenges. We have a difficult time customizing it, but it is similar to other solutions."
"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."
"TWS lacks sophisticated predictive analytics capability. The limited analytics it does offer is predicated on user-defined variables such as job run duration estimates, which if miscalculated render outputs unreliable."
"Maybe a better way to see what a job is waiting on. (Control-M has a "why" function that would be good here)."
"There were real stability issues. The WebSphere process gets hung on TWS masters running TWS 9.1."
"To improve IBM Workload Automation, I suggest enhancing automation features further, as more automation would be beneficial. The product is good enough for my current customers, but improving technical support and pricing would be welcome. We often need quicker responses and better solutions than we can manage manually. These improvements would make the product even better."
"A few things are missing but I can manage without them, such as a cross-reference report."
 

Pricing and Cost Advice

"This is a good product at a fair price."
"The product is reasonably priced, and we don't have any add-ons."
"JAMS is close to the lower end of the pricing models for enterprise scheduling solutions. They are much cheaper than Control-M, as well as some other products that I've used. I also don't know of another solution where you can actually get true, unlimited licensing, where you can have as many instances and as many agents as you want."
"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."
"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 pricing is reasonable."
"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."
"Fortra's JAMS pricing structure has deteriorated significantly since its acquisition by Fortra."
Information not available
"It is about one-third of the cost of a controller."
"The contract is with the customer with whom we are working, so IBM is not directly involved in this."
"To my knowledge, IWA is the only WLA product that will provide "parallel tracking" capability to assist in upgrading from one platform to IWA."
"The solution is a little bit expensive."
"We transitioned from a server license to per job license, and that saved us a lot money."
"The solution's pricing is affordable."
"Pricing depends on the number of agents that you install."
report
Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.
908,877 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Construction Company
12%
Manufacturing Company
8%
Comms Service Provider
7%
No data available
Financial Services Firm
23%
Performing Arts
11%
Construction Company
6%
Retailer
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business15
Midsize Enterprise14
Large Enterprise23
No data available
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise1
Large Enterprise30
 

Questions from the Community

What is your experience regarding pricing and costs for JAMS?
I was not really involved in the pricing, setup cost, and licensing at that level. I am more involved in the technica...
What needs improvement with JAMS?
To improve JAMS, it should resolve the issues with the JD Edwards application and the need for the SSH client connect...
What is your primary use case for JAMS?
My main use case for JAMS is to install, set up, and configure for customers working with JD Edwards application. A s...
Ask a question
Earn 20 points
What needs improvement with IBM Workload Automation?
IBM Workload Automation could be improved by reducing its cost. The maintenance charges have increased significantly,...
What is your primary use case for IBM Workload Automation?
We use IBM Workload Automation ( /products/ibm-workload-automation-reviews ) as a scheduler. We install agents on the...
What advice do you have for others considering IBM Workload Automation?
I recommend IBM Workload Automation as it's a well-established and stable product. However, the cost is a concern. Th...
 

Also Known As

No data available
No data available
IBM Tivoli Workload Scheduler, IBM TWS
 

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
MetLife DHL Express The Clearing House Payments Company ADP Bank of New York Mellon Conway, Inc Carnegie Mellon University
Standard Life Group, Banca Popolare di Milano, A*STAR, ArcelorMittal Gent
Find out what your peers are saying about Flux vs. IBM Workload Automation and other solutions. Updated: August 2026.
908,877 professionals have used our research since 2012.