JAMS Reviews

Name: JAMS
Brand: Fortra
Rating: 4.4 (34 reviews)

4.4 out of 5

34 reviews
96% willing to recommend

What is JAMS?

JAMS offers efficient automation and scheduling with strong capabilities in planning, dependency management, and multi-platform support. Its intuitive interface and robust tools assist in managing complex workflows for enhanced resource allocation.

Get the JAMS Buyer's Guide and find out what your peers are saying about JAMS, Control-M, MuleSoft Anypoint Platform and more!

JAMS is the #5 ranked solution in top Workload Automation solutions. PeerSpot users give JAMS an average rating of 8.8 out of 10. JAMS is most commonly compared to Control-M: JAMS vs Control-M. JAMS is popular among the large enterprise segment, accounting for 59% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a computer software company, accounting for 16% of all views.

Helped 847,862 peers since 2012

Featured JAMS reviews

Rob Grafrath

VP, Enterprise Systems at Capio

The extensibility feature, i.e., the custom execution method ability, is the most valuable feature. We can write a C# interface using the JAMS libraries. We copy the DLLs for the client interface over to our remote desktop and JAMS servers. Then, any of our JAMS users can open up a job definition and see the control developed by our developers. When the job command is issued, it executes our developers' code. I am happy with the exception handling, for the most part. When an exception occurs on one job inside of a series of jobs, it can make that series of jobs stop running, sending an email to someone to let them respond. There is also a monitor view where you can see everything that is currently running and any of the jobs that are currently in an error state. You can find them and try to rerun the job, or cancel it if the job doesn't actually need to be run. JAMS will attach the console logs from anything that has an error on the email that goes to the operators. Also, inside of the job monitor, you can go to the logs and dig down into the details to see what went wrong. It has the ability to use PowerShell to schedule jobs, enable, or disable triggers. The fact that they have JAMS PowerShell cmdlets is useful. This is not central to our use of JAMS, but I appreciate it. While they have extended PowerShell and created cmdlets, I tend to use that when I have to do things like kill all the jobs currently in the schedule, if something catastrophic has occurred. I use them on my test server more than production. On my test server, if I am running a bunch of tests and jobs, but I just want to wipe out the whole scheduler, then I can use a PowerShell command to do that. From time to time, a job is executed and gets stuck in a loop. It gets hung. Maybe the remote system freezes up. Something abnormal happens. It is pretty easy to deal with those. You can see them inside the JAMS monitor because JAMS will automatically calculate the average time that it takes for a given job to execute as long as it has had a few successful runs. The JAMS Scheduler can predict what should take five minutes to run. If it is running for 30 minutes, there is a percentage that shows inside the scheduler that the job is now at 600% of the normal run time. So, you will see this big number, 600% and climbing inside the monitor. You can research that. You can go find the hung process on the source system and respond accordingly. You can set up jobs such that they send alerts or have runaway job limitations. I personally don't tend to use the runaway feature. Our operators notice and respond accordingly to long-running jobs.

Read full review

Patrick Norton

Manager of Reliability Engineering and Security Operations at a computer software company with 501-1,000 employees

JAMS support has been among the most helpful and knowledgeable we've ever worked with. They're always eager to assist and quickly find solutions. While a few minor issues required escalation, we've been able to resolve them all within the current version of JAMS. After initial misuse, we have optimized the use of several agents deployed in our environment. This improvement was made possible through collaboration with internal stakeholders and guidance on JAMS best practices. While agents might appear to directly solve user problems due to their ability to perform custom tasks on machines, in our cases, they operate behind the scenes, unseen by users. JAMS handles exceptions well, especially when calling PowerShell scripts, successfully bubbling up errors. It centralized our job and orchestration management functionalities into a single control plane, providing visibility into previously siloed work. This consolidation streamlined operations and enhanced oversight through a unified dashboard. Additionally, JAMS empowered us to build advanced processes by effectively managing retries, workflows, and sequences. Without JAMS, replicating this functionality would have been manual and inefficient, lacking the comprehensive visibility and control JAMS provides. Data Slack refers to delays in data pipelines caused by disparate and siloed processes. Using JAMS, while powerful for scheduling and orchestration, can exacerbate this issue if teams break down processes into isolated tasks within different tools. This fragmentation leads to data sitting in queues and folders, awaiting processing. To improve efficiency and timeliness, it's recommended to consolidate these fragmented processes entirely under JAMS. This allows JAMS to execute the entire workflow from start to finish within a single execution, eliminating data slack and ensuring timely data delivery. JAMS has helped save IT staff time by automating tasks previously performed with scripts, and its scheduling feature has been particularly useful.

Read full review

Chris Waring

Sr. Vice President, Managed Services and Delivery at Powwr

The most valuable feature is the basic core of the software itself. That is just the level at which you can set scheduling and dependencies between jobs, how everything can be set and scheduled based off of one another, and the ability to run jobs across 25 to 30 different virtual machines. It gives the ability to be able to run jobs on all those servers as well as have them all be visible. In the schedule from one centralized JAMS client location, we can bring up the client interface and see everything that runs across our entire infrastructure, which is really invaluable. We can instantly access all the log files for anything that happens, e.g., if we get any job errors. That is definitely what is most valuable to us. There are some different batch queue features, e.g., we can quickly change the servers where jobs are running. When we made a full move to Azure to be fully cloud based, we had to change all our jobs and the servers that they were going to be running on. The way it had been originally set up was that we used batch queues, where each job would run on a particular server and it would be assigned to the queue, which had the agent definition in it. That told it what server to run on, which was very easy. We didn't have to go through and change thousands of jobs. We only had to go through and change about 20 to 25 different queues, then just point them at different servers. Therefore, it was a very quick and easy change. We have used some of the built-in PowerShell FTP capabilities within JAMS as well as some of the other PowerShell capabilities. We also use the triggers a little bit, when we are watching for files to appear in a particular directory, etc. The exception alerting process is reliable; it works. We don't do anything really fancy with it, and it is mostly based on the actual jobs themselves. For example, if an SQL job, some Windows executable, or an SSIS package that we're running returns an error exit code, JAMS certainly handles that and lets us know. It then does, with the rest of the job surrounding it, what we have configured it to do. From that perspective, it is great. We have some specific instances where if jobs run too quickly or take too long to run, we use the exception alerting process on probably a few dozen different jobs that we have that are really important. The few times that it happened. It has saved us a lot of headaches because it is able to report those exceptions to us. We use a fairly decent amount of the log file exceptions, where you can go in and parse the JAMS job log file for specific entries as it goes through. Then, it can actually error the job out for a job that otherwise might not end in an error. In our case, we wanted to be alerted and have it halt a process if some specific text string shows up in the job log. We have that set up on a number of different jobs, which saves us from a lot of headaches. It has worked out pretty well for helping us handle complex scheduling requirements. We use it in one specific instance where our customers interact with our web-based platform. It has a section where our customers can go in and run one-off versions of their specific processes. So, they will go in and upload a new file, then they want to basically process that file into the system. What they can do is go to the page, upload their file, and then there is a button there that allows them to process it. That button actually links directly into our JAMS server using the JAMS APIs. That will kick off the jobs within JAMS directly. We have it set up so it only allows it to run it during certain times a day. It can check and monitor to see if an instance of a job is already running for that client. If it is, it returns back and tells them that they need to wait for the current one to finish. It returns the actual history from JAMS so they can see all the previous instances of their jobs that have run. This is a really nice feature that our customers really appreciate. It also saves us a lot of time. What would happen in the first couple years before we implemented this, our customers would upload their file, but then they would send in a support ticket for us to run their processes during the day and all our customer processing happens mostly overnight. Therefore, they would want this intraday update of the process. As soon as we implemented this for all of our clients, those support tickets just disappeared. It made a big difference in our ability to support customers.

Read full review

JAMS mindshare

As of April 2025, the mindshare of JAMS in the Workload Automation category stands at 1.7%, up from 1.4% compared to the previous year, according to calculations based on PeerSpot user engagement data.

Workload Automation

PeerAnalyst reports based on JAMS reviews

Type	Title	Date
Category	Workload Automation	Apr 16, 2025	Download
Product	Reviews, tips, and advice from real users	Apr 16, 2025	Download
Comparison	JAMS vs Control-M	Apr 16, 2025	Download
Comparison	JAMS vs Automic Automation	Apr 16, 2025	Download
Comparison	JAMS vs Redwood RunMyJobs	Apr 16, 2025	Download

Title	Rating	Mindshare	Recommending
Control-M	4.4	23.1%	98%	120 interviews Add to research
MuleSoft Anypoint Platform	4.0	4.9%	92%	58 interviews Add to research

Valuable Features

JAMS offers valuable features including ease of use, natural language scheduling, dependency management, batch scheduling, and seamless integration. It provides robust automation capabilities, supports extensive job types, and handles exceptions effectively. Interactive Agents, PowerShell integration, and custom execution methods enhance flexibility. The centralized management interface and detailed logging simplify troubleshooting. JAMS excels in scalability, allowing complex scheduling across various environments, and enhances efficiency, reducing manual interventions and optimizing resource allocation.

"JAMS has helped save IT staff time by automating tasks previously performed with scripts, and its scheduling feature has been particularly useful."
"I appreciate JAMS for its readily available templates that allow me to create and deliver stand-up presentations within minutes quickly."
"The dashboard is intuitive."

Room for Improvement

JAMS needs enhancements in areas like search functionality, UI intuitiveness, and web-based access. Users find the current documentation and support lacking in clarity. Tasks such as automation, exception handling, and integration with other systems need better implementation. The existing reporting and error messaging systems should be refined to improve usability. Performance monitoring and global search capabilities require upgrades. Security permissions and code-driven processes present challenges for some users, highlighting areas for potential development.

"The monitoring of the JAMS product and its performance is an area of concern for me."
"The monitoring of the JAMS product and its performance is an area of concern for me."
"The error messages from JAMS often need clarification, hindering our ability to resolve issues swiftly."

ROI

JAMS significantly enhances productivity by automating processes, reducing labor costs, and saving substantial time. Organizations have increased job volume and automation without needing additional staff. The adoption of JAMS has resulted in substantial cost savings compared to previous systems, offering a robust solution for monitoring and managing jobs. Users report enhanced efficiency, allowing developers to focus on innovation rather than troubleshooting. JAMS has demonstrated consistent value and resource-saving capabilities across various business scenarios.

Pricing

Enterprise users find JAMS pricing competitive, especially when compared to alternatives like Control-M and Tivoli. Initial costs are reasonable, with an annual maintenance fee and optional scalability through additional agents. While some recent price increases have been noted, many users consider the licensing fair and cost-effective, with flexibility in combining processes to optimize job count. The ability to install unlimited agents is a notable advantage, although additional costs may arise for extra services and support options.

"Fortra's JAMS pricing structure has deteriorated significantly since its acquisition by Fortra."
"The pricing is reasonable."
"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."

Popular Use Cases

Organizations primarily use JAMS for automating scheduling tasks such as batch jobs, file transfers, data management, and handling SQL procedures. It centralizes job management across various environments, enabling complex scheduling scenarios for applications like SSIS, Python scripts, and FME. JAMS supports both standalone and interactive jobs, enhancing workflow automation for enterprise applications, nightly processing, workload coordination, and managed file transfers, with deployments often on cloud infrastructure or across multiple servers.

Service and Support

JAMS customer service and support are highly responsive and knowledgeable, often rated nine or ten out of ten. They quickly guide users through troubleshooting steps, offer extensive assistance via email, chat, or screen sharing, and provide instant responses during emergencies. Customers appreciate the proactive approach and skilled help, though support response time can sometimes vary. Many users highlight improved training resources and commend the team for being exceptionally helpful, attentive, and dedicated.

Deployment

JAMS's initial setup is generally easy and efficient, with installation often taking a few hours. Many found instructions clear and support helpful, while some faced SQL permissions issues and documentation challenges. Migration and setup times varied based on complexity and server configurations. With support, even complex deployments are manageable. Though some needed external help, most could perform the setup with minimal assistance, appreciating the straightforward nature and adaptability of JAMS across various environments.

Scalability

Organizations find JAMS highly scalable, managing tens of thousands of jobs daily without issues. Users highlight its ability to seamlessly scale horizontally by adding agents and vertically through server environments. It's suitable for both large and small operations, ensuring efficient job scheduling and automation. JAMS effectively manages workload demands even when expanding infrastructure or migrating jobs across platforms, earning praise for its adaptability and robustness in various settings.

Stability

JAMS consistently demonstrates high stability, rarely encountering crashes or issues. Across multiple organizations, it supports crucial tasks with minimal downtime. Stability improves with each update, though some have experienced slowdowns or interface quirks in older versions. Proper resource allocation ensures optimal performance. Responsibility for any incidents often falls beyond JAMS, such as server limitations or Windows interactions. Users feel confident in JAMS, relying on its robustness and reliability for essential operations.

These insights are based on the in-depth reviews provided by peers to help you make a better buying decision.

Download our JAMS Buyer's Guide for additional reliable information.

Review data by company size

By reviewers

By visitors reading reviews

Top industries

By visitors reading reviews

Computer Software Company

16%

Financial Services Firm

15%

Healthcare Company

Manufacturing Company

Wholesaler/Distributor

Retailer

Government

Energy/Utilities Company

Insurance Company

Non Profit

Comms Service Provider

Logistics Company

Photography Company

University

Educational Organization

Outsourcing Company

Hospitality Company

Real Estate/Law Firm

Legal Firm

Construction Company

Media Company

Performing Arts

Aerospace/Defense Firm

Pharma/Biotech Company

Transportation Company

Music Company

Mining And Metals Company

Marketing Services Firm

Compare JAMS with alternative products

Learn more about JAMS

JAMS stands out for its blend of automation and scheduling capabilities, making it suitable for handling complex workflows across platforms. Its features such as batch scheduling, natural language scheduling, and interactive agents promote seamless integration with other tools like PowerShell. The focus on metrics and notifications ensures users are informed about operational efficiency enhancements. While JAMS is effective in many areas, users report a need for improved simulation for termination processes and a more intuitive client setup. They see potential in enhanced search functions, better exception handling, and greater transparency in custom execution. The current setup challenges like disappearing options and mobile accessibility can affect user satisfaction. Including a fully web-based client and improving documentation could add value.

What are JAMS' key features?

Planning and Scheduling: Coordinates workflows efficiently with advanced scheduling techniques.
Dependency Management: Ensures seamless operation by managing inter-task dependencies.
Interactive Agents: Integrates with PowerShell and other tools to enhance automation.
Natural Language Scheduling: Simplifies job creation with intuitive language use.
Multi-Platform Flexibility: Operates across diverse environments ensuring robust performance.

What benefits should users consider?

Operational Efficiency: Reduction in manual oversight with robust scheduling and integration tools.
Resource Allocation: Efficient management of workflows across multiple timeframes and platforms.
User Satisfaction: Seamless user experience with intuitive interfaces and integration capabilities.
Visibility: Centralized management provides comprehensive oversight over tasks.

Organizations using JAMS for workflow and batch job automation leverage its capabilities for SSIS, SQL procedures, and Python scripts. JAMS supports file automation and managed file transfers across environments like AWS and Azure. Users employ JAMS for data management, reporting, and integration tasks, including handling holiday-aware scheduling for improved task coordination.