We performed a comparison between AutoSys Workload Automation and Fortra's JAMS based on our users’ reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Features: AutoSys Workload Automation is highly regarded for its scalability, user-friendly interface, fast performance, and reliable accessibility. Fortra's JAMS is recognized for its impressive capacity to manage job dependencies, advanced automation features, and comprehensive monitoring and control functionalities.
AutoSys Workload Automation should enhance its integration with cloud services, reporting and comparison of job performance, customization of reporting features and alerts, file transfer job handling, workflow management, and workload window management. Fortra's JAMS should focus on improving its client interface, search capability, training resources, exception handling, browser version compatibility, custom execution methods, integration with Microsoft group-managed service accounts, source control features, documentation, ACL or access permission area, connectivity issues, error notifications, and compliance with the open-source GPG program.
Service and Support: AutoSys is highly regarded for its standardized approach and mature product, while JAMS is known for its fast response time and abundance of documentation and training resources.
Ease of Deployment: Users find the initial setup process for AutoSys Workload Automation to be simple, quick, and uncomplicated, taking approximately 10 minutes or less. Fortra's JAMS setup is also straightforward and easy, with users able to quickly deploy tasks by following instructions on the webpage.
Pricing: AutoSys Workload Automation has a yearly subscription and an annual license. It requires an additional cost for agents, while the server setup has a one-time license and an annual maintenance cost. Fortra's JAMS has an initial license cost for the first year, along with an annual maintenance cost. Users consider JAMS to be reasonable and cost-effective when compared to similar products.
ROI: AutoSys Workload Automation and Fortra's JAMS both offer significant benefits in terms of time savings, increased productivity, and cost-effectiveness. AutoSys provides improved reliability, scalability, and enhanced visibility and control, while JAMS offers automation and improved process robustness.
Comparison Results: AutoSys Workload Automation is preferred over Fortra's JAMS. Users praise AutoSys for its scalability, ease of use, speed, and availability. They appreciate its user-friendly interface, robustness in triggering jobs, and ability to handle large volumes. They also like its simplicity, stability, and ability to connect different software processes.
"The most valuable features of AutoSys Workload Automation are the file transfer protocol and file watcher. The solution has a user-friendly user interface. It is very simple to use. You have a scope of all your jobs, jobs are what you call tasks that you will automate in the solution. It lets you monitor everything in these jobs."
"Running anything in crontab, you need to put a lot of logic into it to make it work. With this product, you don't have to worry about it. You have the schedule object where you put all the dates or holidays in it, and it does it for you."
"It has helped to simplify cross-dependency between MVS and Open systems jobs."
"We automate recurring processes, keeping track of IT processes controlled worldwide."
"Inherit Dependencies feature reduces scheduling errors for holiday processing."
"We need to have things run in a very sequential order, so it is very useful that we can schedule the work flows."
"It is stable, it works, and it does what it is supposed to."
"AutoSys Workload Automation is a stable solution."
"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."
"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."
"Being able to create a series of chained jobs, which are basically linked jobs is valuable."
"It's a full-featured job scheduling tool. The part that I liked the best was the support team. This tool was new, and we were all learning it and setting up the different jobs that were complex in nature. Their support team was very responsive in helping us out through the setup and resolving the issues. They have been incredibly awesome."
"I find the historical tracking feature of JAMS invaluable for reviewing past events."
"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."
"The product is easy to use."
"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."
"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."
"It would be helpful to be able to monitor and manage workload windows so we could minimize downstream applications. This would allow us easier access to the applications."
"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."
"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."
"It lacks support and integration with cloud computing platforms."
"Ease of implementation for upgrades."
"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."
"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."
"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."
"Sometimes the UI is not the most responsive I've ever used. But because it does its job, I don't complain."
"The product does not allow the users to cut and paste the job names from the screen."
"The tabs in the JAMS file transfer could be clearer. It would help us demonstrate to our client that JAMS not only automates jobs but also does fast transfers, and it's an alternative that supports and filters different kinds of platforms. Filtering file transfers will be highly beneficial to them."
"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."
"The only thing that they could improve on is the fact that they don't have a browser version of JAMS. They've got all the bits and pieces there if you want to build your own web version of it. It does come with a web client, but it's pretty clunky. They could improve on that."
"If there were a softcover book on how to really take advantage of all of JAMS' tools, I would buy it. I do better with training books than online searching, so a book would be helpful."
AutoSys Workload Automation is ranked 6th in Workload Automation with 79 reviews while Fortra's JAMS is ranked 5th in Workload Automation with 27 reviews. AutoSys Workload Automation is rated 8.4, while Fortra's JAMS is rated 9.0. The top reviewer of AutoSys Workload Automation writes "Helps us manage complex workloads, reduce our workload failure rates, and save us time". On the other hand, the top reviewer of Fortra's JAMS writes "We can scale up our organization's scheduling and automation without having to add staff to the department". AutoSys Workload Automation is most compared with Control-M, IBM Workload Automation, Red Hat Ansible Automation Platform, Automic Workload Automation and Stonebranch, whereas Fortra's JAMS is most compared with Control-M, Tidal by Redwood, Redwood RunMyJobs and VisualCron. See our AutoSys Workload Automation vs. Fortra's JAMS report.
See our list of best Workload Automation vendors.
We monitor all Workload Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.