ActiveBatch by Redwood vs AutoSys Workload Automation comparison

ActiveBatch by Redwood vs. AutoSys Workload Automation

Download the complete report

Helped 879,927 peers since 2012

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

Mindshare comparison

As of January 2026, in the Workload Automation category, the mindshare of JAMS is 2.6%, up from 1.6% compared to the previous year. The mindshare of ActiveBatch by Redwood is 2.8%, up from 2.1% compared to the previous year. The mindshare of AutoSys Workload Automation is 8.4%, down from 15.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.

Workload Automation Market Share Distribution
Product	Market Share (%)
JAMS	2.6%
AutoSys Workload Automation	8.4%
ActiveBatch by Redwood	2.8%
Other	86.2%

Workload Automation

Featured Reviews

reviewer2770605

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.

Read full review

Abdul_Samad

Application Administrator Lead at Bluestem

Manages thousands of jobs daily and reduces downtime through secondary node support

The current feedback I receive from my end users regarding ActiveBatch by Redwood highlights issues with the tabs or panes during job modification. When the next user monitors it, they need to close the pane or job and reopen it to see the changes reflected. If the end user makes an update, it will not be visible unless they start from the beginning again. Implementing a refresh button would be helpful for real-time updates when the end user needs to see changes immediately. We currently face issues with the web console of ActiveBatch by Redwood. When users operate through an RDP session, every user has their own ActiveBatch by Redwood application. However, on the web console, users encounter daily activity issues where the job instances do not appear or update correctly, and they cannot view the latest logs. This issue is only present on the web console, as the application itself works without any problems. ActiveBatch by Redwood can be improved by adding more features, as we are not currently handling cloud-based applications like S3 buckets and Azure. Connecting to these cloud platforms would be a helpful enhancement.

Read full review

Pavan Katta

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.

Read full review

Quotes from Members

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

Pros

"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."

"The most valuable feature is the easily accessible data in the database because we run a lot of SQL scripting against the database."

"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."

"JAMS has improved my organization by taking a myriad of manual processes and allowing us to automate them. It enables our folks to focus more on tasks that require their human intelligence and their creativity and less on just mundane tasks. It increases efficiency, accuracy, and consistency."

"The most valuable feature of JAMS is its user-friendly interface, especially after upgrading from version six to seven."

"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."

"Being able to create a series of chained jobs, which are basically linked jobs is valuable."

"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."

More JAMS pros

"The user interface is really incredible."

"Error Handling is one of the best standout features of ActiveBatch."

"Since we are no longer waiting for an operator to see that a job is finished, we have changed our daily cycle from running in eight hours down to about five. We had a third shift-operator retire and that position was never refilled."

"ActiveBatch can automate predictable, repeatable processes very well. There is no real trick to what ActiveBatch does. ActiveBatch does exactly what you would expect a scheduling piece of software to do. It does it in a timely manner and does it with very little outside interference and fanfare. It runs when it is supposed to, and I don't have to jump through a bunch of hoops to double check it."

"ActiveBatch provides summary reports and logs for further analysis and improvements in monitoring servers, which is very handy."

"The best feature that ActiveBatch by Redwood offers is the user interface."

"The automation feature is a very valuable feature as the associates do not have to worry about performing repetitive tasks (i.e. endpoint security scans on a daily basis) that would take several hours to complete on a daily basis."

"Managing the workload and monitoring the tasks were very difficult with manual interventions. Now, by using ActiveBatch, the process is automated and it runs tasks on a scheduled basis."

More ActiveBatch by Redwood pros

"The flexibility in solving job scheduling challenges allows us to successfully integrate an acquired business’ fiscal close with our own, even though there is a lot of variance as to when they run in the calendar month."

"The initial setup is easy."

"It has improved my organization by automating IT applications."

"Automation of patch process."

"It works constantly and is pretty seamless. You do not have to open up many support tickets."

"It has helped to simplify cross-dependency between MVS and Open systems jobs."

"The web UI is beneficial and the granular security policies allow us to cover all of our audit requirements."

"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."

More AutoSys Workload Automation pros

Cons

"JAMS notifications for hung jobs could be improved."

"The error messages from JAMS often need clarification, hindering our ability to resolve issues swiftly."

"JAMS has built-in reporting. I've never really used it. I tried using it a few years ago and I couldn't figure it out. It was wonky. It could be improved upon."

"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."

"I want JAMS to implement a global search function."

"We have had a lot of people working from home who can't always connect to the JAMS server. We use VPN, as most companies do, and we have it set up so that everybody can access the JAMS server. But many times, our people cannot access it... JAMS could do a better job of telling you what the problem is when you try to log in to the server."

"Fortra is getting much better with documentation and examples, but there is still room for improvement."

"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."

More JAMS cons

"The documentation is very limited, and it can be improved."

"There are some issues with this version and finding the jobs that it ran. If you're looking at 1,000 different jobs, it shows based on the execution time, not necessarily the run time. So, if there was a constraint waiting, you may be looking for it in the wrong time frame. Plus, with thousands of jobs showing up and the way it pages output jobs, sometimes you end up with multiple pages on the screen, then you have to go through to find the specific job you're looking for. On the opposite side, you can limit the daily activity screen to show only jobs that failed or jobs currently running, which will shrink that back down. However, we have operators who are looking at the whole nightly cycle to make sure everything is there and make sure nothing got blocked or was waiting. Sometimes, they have a hard time finding every item within the list."

"We have faced a couple of issues where we were supposed to log a defect with ActiveBatch. That said, the Active batch Vendor Support is very responsive and reliable."

"Whenever there is an overload, we are seeing crashes happening."

"A nice thing to have would be the ability to comfortably pass variables from one job to another. That was one of the things that I found difficult."

"They should offer pricing that is more affordable."

"It does have a little bit of a learning curve because it is fairly complex. You have to learn how it does things. I don't know if it's any worse than any other tool would be, just because of the nature of what it does... the learning curve is the hardest part."

"An area for improvement in ActiveBatch Workload Automation is its interface or GUI. It could be a little better. There isn't any additional feature I'd like to see in the tool, except for the GUI, everything looks good."

More ActiveBatch by Redwood cons

"Quick search feature and job analysis could be improved."

"The graphical interface can be improved."

"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."

"The visibility and control features are somewhat limited."

"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."

"CA Workload Automation is not part of CA's strategic vision going forward."

"I would like to see two-factor authentication, since you see a lot of companies in the news for security breaches. That is a really big thing for us."

"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."

More AutoSys Workload Automation cons

Pricing and Cost Advice

"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."

"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."

"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."

"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."

"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 pricing is reasonable."

More JAMS pricing and cost advice

"The pricing was fair. There are additional costs for the plugins. We have the standard licensing fees for different pieces, then we have the plugins which were add-ons. However, we expected that."

"Currently, we are paying approximately $7,000 yearly, which includes support."

"The price was fairly in line with other automation tools. I don't think it's exorbitantly expensive, relatively speaking."

"ActiveBatch is currently redesigning themselves. In the past, they were a low cost solution for automation. They had a nice tool that was very inexpensive. With their five-year plan, they will be more enhancement-driven, so they're trying to improve their software, customer service, and the way that their customers get information from them. In doing that, they're raising the price of their base system. They changed from one pricing model to another, which has caused some friction between ActiveBatch and us. We're working through that right now with them. That's one of the reasons why we're why we were evaluating other software packages."

"I don't think we've ever had a problem with the pricing or licensing. Even the maintenance fees are very much in line. They are not excessive. I think for the support that you get, you get a good value for your money. It's the best value on the market."

"I like ActiveBatch Workload Automation's licensing model because they're not holding you down on an agentless model or agent model, where every server needs to have an agent. That's the main selling point of the solution and I hope they stay that way."

"It allows for lower operational overhead."

"If you compare ActiveBatch licensing to Control-M, you're looking at $50,000 as opposed to millions."

"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 price of this solution is reasonable and there is an annual license required."

"We paid to use the solution monthly."

"It is overpriced."

"CA pricing has been a problem, and not looked upon favorably here at all."

"Validate how many agents you need beforehand."

"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."

"There is an annual license to use AutoSys Workload Automation."

More AutoSys Workload Automation pricing and cost advice

See which vendors are best for you

Use our free recommendation engine to learn which Workload Automation solutions are best for your needs.

See recommendations

879,927 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Financial Services Firm

15%

Computer Software Company

12%

Manufacturing Company

11%

Healthcare Company

Financial Services Firm

15%

Insurance Company

Retailer

Manufacturing Company

Financial Services Firm

42%

Manufacturing Company

Retailer

Insurance Company

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

By reviewers
Company Size	Count
Small Business	11
Midsize Enterprise	8
Large Enterprise	18

By reviewers
Company Size	Count
Small Business	11
Midsize Enterprise	13
Large Enterprise	47

By reviewers
Company Size	Count
Small Business	13
Midsize Enterprise	5
Large Enterprise	77

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?

They recently switched to subscription-based pricing, which increased. The price is fair considering the functionalit...

What needs improvement with JAMS?

As far as we are using JAMS version 6, it looks good and there is nothing major to add about it. Everything is functi...

What is your experience regarding pricing and costs for ActiveBatch Workload Automation?

My experience with pricing, setup cost, and licensing for ActiveBatch by Redwood has been great; we recently renewed ...

What needs improvement with ActiveBatch Workload Automation?

I believe ActiveBatch by Redwood could be improved because the UI could be modernized.

What is your primary use case for ActiveBatch Workload Automation?

My main use case for ActiveBatch by Redwood is file processing. I use ActiveBatch by Redwood for file processing for ...

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 is your experience regarding pricing and costs for AutoSys Workload Automation?

It is reasonably priced compared to the market.

Redwood RunMyJobs vs JAMS

Comparisons

Control-M vs JAMS

Compared 20% of the time

Compared 11% of the time

Stonebranch vs JAMS

Compared 10% of the time

Automic Automation vs JAMS

Compared 8% of the time

Tidal by Redwood vs JAMS

Compared 4% of the time

More JAMS Competitors

Control-M vs ActiveBatch by Redwood

Compared 12% of the time

MuleSoft Anypoint Platform vs ActiveBatch by Redwood

Compared 11% of the time

Stonebranch vs ActiveBatch by Redwood

Compared 10% of the time

Redwood RunMyJobs vs ActiveBatch by Redwood

Compared 8% of the time

More ActiveBatch by Redwood Competitors

Control-M vs AutoSys Workload Automation

Compared 32% of the time

Automic Automation vs AutoSys Workload Automation

Compared 8% of the time

Stonebranch vs AutoSys Workload Automation

Compared 8% of the time

IBM Workload Automation vs AutoSys Workload Automation

Compared 6% of the time

Astro by Astronomer vs AutoSys Workload Automation

Compared 2% of the time

More AutoSys Workload Automation Competitors

Product Reports

JAMS

Download JAMS product report

ActiveBatch by Redwood

Download ActiveBatch by Redwood product report

AutoSys Workload Automation

Download AutoSys Workload Automation product report

Also Known As

No data available

ActiveBatch

CA Workload Automation, CA Workload Automation AE

Interactive Demo

JAMS Software

Demo not available

ActiveBatch by Redwood

Demo not available

Broadcom

Overview

JAMS is an automation and job scheduling solution designed for workflow optimization, catering to businesses large and small with flexible licensing and integration options.

Offering both Core and Advanced packages, JAMS supports a range of environments from small teams to large-scale operations. Its standout features include integration with platforms like PowerShell, SQL, and SAP, coupled with capabilities such as dependency management and natural language scheduling. JAMS simplifies job management, centralizes workflows, and boosts productivity with its robust automation features. Customizable workflows and insightful logging make it adaptable for diverse needs, supported by responsive customer service ensuring seamless operations.

What are JAMS's key features?

Automation & Scheduling: Flexible automation helps manage complex job schedules efficiently.
Integration: Connects seamlessly with platforms like SQL Server, SAP, and Python for diverse applications.
Centralized Job Management: A unified interface for handling thousands of jobs daily.
Dependency Management: Supports complex workflows with efficient dependency tracking.
Insightful Logging: Provides detailed logs and notifications for precise task execution.

What benefits should users look for in JAMS reviews?

Enhanced Productivity: Automates repetitive tasks, freeing up resources for strategic initiatives.
Scalability: Flexible licensing models grow with business size and needs.
Efficient Workflow Automation: Streamlines job orchestration across environments.
Responsive Support: Helps ensure smooth operations with quick troubleshooting.

In industries, JAMS is employed for automating workflows and managing batch jobs. Organizations utilize it for SSIS, SQL Server tasks, file transfers, and integrating with vendor systems, achieving efficient file automation and data management. Scheduler enables precise execution of thousands of tasks daily, enhancing operational efficiency.

JAMS Software

ActiveBatch by Redwood enhances efficiency with features like job scheduling, integration, and real-time monitoring. It supports diverse platforms, automates tasks, and offers a single-pane view with robust security.

ActiveBatch streamlines automation by offering drag-and-drop functionality, pre-built job steps, and native integrations. Its customizable workflows and alert system aid in managing complex workloads like data processing and server monitoring across hybrid environments. While it effectively reduces manual errors and enhances productivity, areas like navigation and support for cloud platforms need enhancement. New users may face challenges due to its complexity and steep learning curve, and further improvements in reporting, mobile access, and training could provide additional support to users.

What important features does ActiveBatch offer?

Comprehensive Job Scheduling: Manages and automates complex workloads efficiently.
Integration Capabilities: Seamlessly connects with different platforms and applications.
Real-time Monitoring: Offers a single-pane view for quick issue identification.
Customizable Workflows: Tailors processes to specific organizational tasks.
Robust Alert System: Ensures timely notifications for critical events.
Data Protection: Incorporates strong security measures for secure operations.

What benefits should be considered when evaluating ActiveBatch?

Enhanced Efficiency: Automates repetitive tasks, reducing manual intervention.
Improved Productivity: Streamlines processes across hybrid environments.
Error Reduction: Decreases likelihood of manual errors.
Platform Support: Provides integration with diverse systems.

In finance, ActiveBatch is implemented for orchestrating batch processes and data management. The healthcare industry utilizes it for automating patient data updates and server monitoring, while the retail sector benefits from file transfers and inventory management automation.

ActiveBatch by Redwood

AutoSys Workload Automation efficiently manages complex workloads across platforms, offering high availability and seamless platform integration. Its reliability and scalability are valued for enterprise-level automation, enhancing job management and reducing manual effort with robust scheduling and advanced security.

AutoSys Workload Automation is known for its user-friendly capabilities, effectively handling cross-platform job scheduling with mainframe integration. It supports high availability, ensuring reliable performance for critical operations. Despite enhancements needed in its GUI and integration capabilities, AutoSys remains effective for batch processing, file transfers, ETL, and managing dependencies across servers and applications. Improvements are suggested for deployment complexity and monitoring features. More effective licensing and scalability solutions, along with modern subscription models and cloud integration, could address cost and automation barriers.

What are AutoSys Workload Automation's key features?

Robust Scheduling: Automates job scheduling across multiple platforms efficiently.
Advanced Security: Ensures secure management of workloads.
High Availability: Maintains performance during critical operations.
Platform Integration: Seamlessly integrates with diverse systems.
Scalability: Supports growing enterprise demands.

What benefits should users expect from AutoSys Workload Automation?

Reduced Manual Effort: Minimizes manual task management.
Enhanced Job Management: Improves oversight and control over job processes.
Flexibility in Scheduling: Offers adaptable scheduling and monitoring options.
Reliability: Consistent job execution without failures.
Security: Protects enterprise-level operations.

In industries like banking, insurance, and retail, AutoSys Workload Automation facilitates 24/7 automated job execution, ensuring smooth task automation. It allows companies to manage enterprise workloads effectively, catering to batch processing, file transfers, and handling job dependencies in a consistent manner.

Broadcom

Sample Customers

Teradata, Arconic, General Dynamics, Yum!, CVS Health, Comcast, Ghiradelli, & Boston’s Children’s Hospital

Informatica, D&H, ACES, PrimeSource, Sub-Zero Group, SThree, Lamar Advertising, Subway, Xcel Energy, Ignite Technologies, Whataburger, Jyske Bank, Omaha Children's Hospital

Gaumont, Mercantil do Brasil, CCEE, Hanwha Life

ActiveBatch by Redwood vs. AutoSys Workload Automation