Event-Based Scheduling

Use Triggers to Kick Off Jobs Based on Events, Files, and Other Events

How Event-Based Scheduling Works

An enterprise job scheduler that includes event-based scheduling options maximizes your resources by uniting your disparate platforms and their respective job schedules and critical business applications and allowing them to become reactive with one another. A file transfer or report completion could trigger Job A. Then from there, Job A’s completion immediately triggers Job B, which could trigger Job C. This creates a holistic job schedule that coordinates—and therefore makes the most of—the resources you already have in place.

JAMS provides event-based job scheduling to allow jobs and processes to be triggered by events such as file transfers, system startups, runaway processes, or user-defined events.

Benefits of Event-Based Scheduling

You have the most current data and files in your workflows
You can cut the built-in slack time between jobs from your schedule, meaning everything runs more efficiently
You get visibility into every job running
If a job fails, the process will halt, and you’ll get an alert to fix the problem before another job runs with incorrect or incomplete data.

Types of Job Triggers

File Triggers

JAMS event-based scheduling has built-in triggers which enable users to execute processes on any operating system based upon files being created, modified or deleted.

Status Triggers

JAMS can check exit status and determine the appropriate job to trigger based on conditional flows. JAMS event-based job scheduling allows for jobs to have expected run times so that they can be monitored. Alerts can even be triggered to the appropriate person to notify him/her that a job is waiting for that person to release a file.

Alerts can be triggered when an expected event does not occur within a specified time window. With JAMS you can, as an example, alert a vendor or supplier that the system is waiting for their action or a file.

Event Triggers

Multiple triggers can be set on jobs so that jobs are triggered based on events, a specific date and time, or even from previous jobs that have failed or succeeded. With JAMS sequences, users can create workflows that depict the dependencies that exist between various processes that are being managed through JAMS.

Variable Triggers

JAMS event-based job scheduling can also interrogate data by using JAMS Variables and allow specific data to be used as an alternative approach to an event based job trigger. JAMS Variables can be used between jobs so that data is passed throughout the workload.

Event-Based Scheduling vs. Time-Based Scheduling

The most common ways to set your job schedule is event-based and time-based scheduling. Time-based scheduling is a simple way to schedule jobs by designating a time for your process to run. However, event-based scheduling provides a more robust way to streamline your workflows with greater reactivity. Instead of letting your processes sit idle until a set time with time-based scheduling, event-based scheduling allows jobs to begin immediately after another event or process has occurred. This ensures that processes complete in the right order to avoid complications and problems with your IT workflows.

Now, we’re leveraging file triggers. As soon as something happens in the database, it writes a file to the server. JAMS sees the file and it kicks off another job in real-time.

Read The Case Study

Rishi Maharaj, Senior Systems Administrator

Customers Rate JAMS a Leader

Top-notch, thorough, friendly, and responsive — these are just a few words used to describe JAMS Support.

JAMS enables efficient workload management and provides an unparalleled customer support experience. Rely on JAMS for expert help, whenever you need it.

Read Our Reviews on G2

Try Event-Based Scheduling. Start Your 14-Day Free Trial Today.

Download JAMS