TrustRadius Insights for JAMS are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Workflow Modules: Users have found the Workflow Modules in Jams to be tremendously helpful for sequential processing of files, allowing for efficient management and execution of tasks in a structured manner. The clear organization provided by these modules has been praised for streamlining workflows and enhancing productivity.
Execution Options: Some users have highlighted that multiple execution options from Powervshell to SQL stored procedures to SSIS packages were considered easy to use for legacy code executions, offering flexibility and compatibility with various systems. This variety of execution choices caters to different user preferences and technical requirements, contributing to a seamless operational experience.
Alert Notifications Feature: The Alert Notifications feature in Jams, allowing paging someone when a job fails, has been deemed extremely useful by users for timely issue resolution and operational efficiency. This proactive notification system ensures prompt responses to potential problems, minimizing disruptions and optimizing workflow continuity.
We are moving away from CA7 on our AS400 platform and onto JAMS. There are thousands of business critical batch jobs that run on a daily basis that need to be scheduled and monitored. Our developers are finding JAMS a lot easier to manage and write jobs for than using the old JCL format. Scheduling is easy and we're working towards a fuly automated solution with errors being logged automatically and notification calls to on-call staff also being automated, doing away with a 24/7 eye's on requirement.
Pros
integrate with mulitple OS's
Simplified job creations and extended job attributes that can be applied to all jobs from a parent folder
multiple calendars (great for retail businesses where there are financial dates and retail trading dates to be met)
Creating schedules using simplified language
Cons
Training is quite expensive and could be streamlined
adding GoAnywhere SFTP product as an add-on module instead of a separate product
Likelihood to Recommend
We looked at a number of products and ran a POC against a rival product and this was the hands down winner, a number of business areas agreed with our findings. Using JAMS has a small learning curve but most of our developers needed very little help in getting going.
VU
Verified User
Project Manager in Information Technology (10,001+ employees)
JAMS runs workload automation for Red Lobster (RL) financial systems, HR, business intelligence, supply chain, restaurant polling, and most other system processes. JAMS provides an excellent way for all of the RL systems to interoperate sharing resources, cloud storage, databases, etc. through JAMS workflows instead of system silos with their own independent automation and integration solutions.
Pros
Very reliable and robust platform.
JAMS Support is superb and always helpful.
JAMS is easy to work with and provides creative solutions for a wide variety of challenges.
Cons
Being able to hot swap for failover has always been a challenge for RL JAMS. This presents challenges when performing planned system outages. We never have been able to perform outages without bringing RL JAMS down.
We are on JAMS v6.4.74 and it would be nice to have more capability to perform remote JAMS admin through mobile devices. I think JAMS 7x has this.
Red Lobster has had to create some custom alerting for JAMS scheduling failures over the years, and it would be nice to have better SMS alerting built into JAMS.
Likelihood to Recommend
JAMS is well-suited for Red Lobster because of the tight coupling between most of the major systems here and the need to have a universal scheduling platform - JAMS does this.
VU
Verified User
Administrator in Information Technology (10,001+ employees)
We have scheduled multiple workflow jobs to handle the formatting, archiving, and processing of files. Additionally, we use PowerShell jobs to automate the uploading of files to SharePoint. File transfer jobs are also in place to connect to the vendor's SFTP server for file uploads and downloads. A series of sequence jobs ensures that all tasks are executed in the correct order. SSRS reports are scheduled to run upon the completion of specific SSIS packages. Lastly, Python jobs are used to trigger email notifications to a list of users based on data from an Excel file.
Pros
Workflow, for each loop...all options in toolbox
Scheduling Jobs depends on another Job completion and file watch Jobs...etc
Supports to schedule SSRS Reports and SSIS packages
Support Program languages like PowerShell and Python
Cons
Downloading the latest files from sFTP location
Querying the Job execution History
Querying the Job logs
JAMS Web Access has a lot of limitations
Likelihood to Recommend
Scheduling multiple workflow jobs PowerShell jobs to automate the uploading of files to SharePoint. File transfer jobs to connect to the vendor's SFTP server for file uploads and downloads. Sequence jobs ensure that all tasks are executed in the correct order. SSRS reports are scheduled to run upon the completion of specific SSIS packages. Supporting Python to automate few processes.
VU
Verified User
Engineer in Information Technology (1001-5000 employees)
The N-tier application we use has jobs coming from multiple servers 24 hours a day. JAMS managees all of those and allows us to set alerts, to set automatic retires and send notifications. The history is fantasic way to get a quick view of what failed over the day without checking every job. There are so many funtionalities we have yet to use, such as running sql jobs or CMD scripts. Fantasic product, highly recommended.
Pros
history
alerts
auto-resubmits
Cons
a wizard for setting up jobs
a folder with the failed job notifications, easy to find
an easier way to set web interface (back to the wizard)
a set of video walk throughs with examples for each type of scheduling
Likelihood to Recommend
The best environment is where you have lots of jobs from lots servers and need a history of detailed failures. Our web server, SQL server and App server all have applications that need scheduling. It wouldn't be necessary if you have a just a handful of jobs for which you can use task manager.
JAMS was used to execute JDE batch processing as well as run Oracle stored procedures and Powershell scripts
Pros
Ability to manage jobs across multiple platforms
Great error handling, alerting, recovery and management
Scripting options with Powershell scripts provided enhanced capability
Ability to manage, define and schedule jobs through a single interface
Cons
Installation process needs improvement due to minor bugs specifically for JDE integration
Ability to create Powershell scripts from GUI schedules would be nice
Updated documentation to cater for current release (found some gaps on occasion)
Likelihood to Recommend
Native JDE support and integration along with error handling as well as enabling us to re-run jobs and set-up and configure dependencies.
Detailed alerting enabling us to determine when jobs or sequences fail and address accordingly. Scalable and high availability solutions ensuring minimal interruptions. Competitive pricing with other products making it a preferred solution.
VU
Verified User
Consultant in Information Technology (501-1000 employees)
Schedule tasks that include a nightly cycle to copy data from its database to the data warehouse, copy files, run batch files, run iCEDQ data comparison jobs, and run other in-house jobs.
Pros
Respond promptly to tickets.
Allow for upgrades.
Add new clients/agents.
Cons
Add desired enhancement promptly.
Evaluate migration workload.
HA failover gracefully.
Likelihood to Recommend
JAMS is not the best solution when you have more than 50 tasks in a workflow. It is difficult to see where the workflow fails, and the light color board is difficult to find.
We use JAMS as the scheduler for almost all of our critical batch processing needs. We needed a solution which would effortlessly allow for file transmission via FTP, ability to send files via email, robust alerting for job failures, and the ability to run custom .NET jobs on a schedule. JAMS does all of this with little effort and maintenance.
Pros
Support
Credential management
Scheduling, including dependencies
Cons
Better separation of environments (production vs qa vs development)
Built in job runbook (with schedules, job information, etc)
Web client could be improved
Likelihood to Recommend
JAMS is fantastic at what it can do. While there are some things that it can't, JAMS has the ability to run custom jobs through the "Execute CMD" feature, so as long as you are able to create those jobs JAMS should be perfect for most environments. For smaller or less experienced teams it may be difficult to get JAMS to do every automation task needed, but there is an addon that brings some of that functionality to JAMS (we do not use it currently).
VU
Verified User
Administrator in Information Technology (51-200 employees)
Systems automation like downloading files, moving them kicking off scripts that do other processing. End user automation like sending reports via emails, downloading files to file shares
Pros
Workload Processing
Error Alerts
Job Scheduling
Cons
Can not search for jobs or objects.
Cannot do version control of code
not easy to test changes. Need to make a code change, deploy, then submit job, then open monitor, then check job. if fails, come back to job definition and restart process. I think this is very cumbersome
Likelihood to Recommend
Well suited: Easy to use with point and click based setup. Monitoring of jobs are easy Less appropriate: In my experience, does not fit well into a modern toolset and technology stack
VU
Verified User
Director in Information Technology (51-200 employees)
We have a central management of JAMS, but various teams use it. We connect to about 50 servers and run about 30,000 jobs a day. We use it to run jobs and workflows to automate scheduling and work management.
Pros
It allows for very complex workflows.
JAMS is very customizable, for times, emails, etc.
JAMS has an open database to build complex queries against jobs and history.
JAMS queue process allows us to pause groups of jobs at a time.
Cons
On complex jobs it might be challenging to find where in the flow a job is located.
JAMS security model is very robust but has troubles at times.
Because of robust configurations, some views (lists) are missing data, so it would be nice to have on it.
Likelihood to Recommend
I have been working with JAMS for over ten years. We have not encountered any situations for scheduling and managing jobs that JAMS would not accommodate.
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.
Likelihood to Recommend
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.
VU
Verified User
Director in Information Technology (501-1000 employees)