JAMS has been the perfect scheduler for our environment.
Updated April 21, 2025

JAMS has been the perfect scheduler for our environment.

Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with JAMS

We have been using JAMS to control jobs and processes for both Windows and Linux systems. Some are as simple as just triggering a job to start at a given time. Others are looking for the existence of a file added by a user or by another process or as the output of a previous job. We use the condition codes to determine whether to go on to the next setup, start a child process, or notify someone of an error. Some of our error routines call recovery processes to try and fix the problem automatically before informing someone.

Pros

  • Reboot systems, stop and start services.
  • Automate ETL processes.
  • Automate the generation of reports, both printed and emailed.
  • Rebuild/update dashboards.

Cons

  • We have found JAMS to be much easier to use than our previous system and have not had any issues.
  • JAMS was less expensive than our previous Schedler.
  • JAMS is far easier to use than other products that we looked at.
  • JAMS is very OS agnostic, and we have now consolidated many locally scheduled jobs in one place.
  • Having all of the jobs in one place allows us to monitor our processes easily. Also, it is much easier to update and control the many jobs running across hundreds of systems.
  • The consolidation of schedulers and the different ways of scheduling jobs have made it not only easier but also much more cost-effective.
The mix of clientless and installed clients makes it very easy to control our costs while still being able to manage all of our systems. We can choose between running a couple of jobs with JAMS without an agent or adding a full client agent to get the additional functionality is worth the expense.
We do not need to use JAMS support very often. The server and clients have been very stable and reliable. Upgrades are not required very often and can be easily pushed out from the server, and we have never had a problem with them. But the couple of times I have opened a ticket to learn how to make something new work, they have been responsive and friendly.
JAMS was much more cost-effective and easier to use. JAMS allowed us to centralize our job scheduling more fully. Converting from our previous, very limited scheduler to JAMS would be far more accessible than Automox.

Do you think JAMS delivers good value for the price?

Yes

Are you happy with JAMS's feature set?

Yes

Did JAMS live up to sales and marketing promises?

Yes

Did implementation of JAMS go as expected?

Yes

Would you buy JAMS again?

Yes

We have been using JAMS for several years, and it is relatively easy to get up to speed. It works well whether the target system has the JAMS client installed. This allows us to manage the simple scheduled restart of the system without going to the expense of installing the client. Simple processes that require little feedback don't need the client. We can still do simple logging without the client. We get much more control and input from the client, and we install it on systems with more complex requirements for more jobs.

JAMS Feature Ratings

Workload Automation
9.3
Multi-platform scheduling
10
Central monitoring
10
Logging
10
Alerts and notifications
9
Analysis and visualization
8
Application integration
9

Using JAMS

6 - Business Intelligence development and reporting. ETL of data between different systems and networks. Monitoring of the receipt of data from 3rd party sources.

Server Administration/Operations for server maintenance both in Linux and Microsoft Windows. This includes data management, rebooting of servers and running of security and other reports. Simple report distribution via email after the jobs complete.
2 - We run JAMS on Windows. We have a server administrator responsible for maintaining the server OS as well as apply JAMS updates and pushing them out to the client agents. That person also monitors the JAMS system and its agents to make sure that the environment is running correctly. They are also responsible for any troubleshooting of the JAMS process. They are the lead for creating and supporting jobs running on our Windows and Linux servers. They are able to create/troubleshoot both Windows and Linux scripts. This person also supports other administrators who also create administrative and maintenance jobs.

A lead BI developer who is responsible creating/troubleshooting BI jobs. They also support other developers that are creating jobs in the BI environment.
  • Data transformation.
  • Server maintenance/operations
  • Data migration.
  • Running and distribution of reports.
  • We did not expect to be running near as many jobs as we are.
  • As we move to the cloud, we are starting to use JAMS to better integrate on-prem resources and cloud resources.
JAMS is a critical resource free up people to do other things and ensuring that processes and tasks are run consistently. We are also confident that procedures are run consistently and on time or as soon as the necessary data is available. With automated job failure notification, we are not required to check that jobs are running correctly.

Comments

  • Peter Hegland | TrustRadius Reviewer
    Peter Hegland
    commented a year ago
    Hi - Thank you so much for taking time to leave us a review. Also, thank you for being a loyal customer of JAMS. I am the Managing Director/General Manager for JAMS. If you would like to discuss anything JAMS or how we can do better and improve please reach out. My email is: peter.hegland@fortra.com Best, Peter Hegland

More Reviews of JAMS

  1. Home
  2. Workload Automation Software
  3. JAMS Reviews
  4. User Review of JAMS