Events and different types in Autosys and also how it works

Events

Events are fundamental to Autosys (now part of Broadcom's AutoSys Workload Automation) as they drive job scheduling, dependencies, and workflow automation. 

Below is a detailed breakdown of how events function in Autosys:

What Are Events in Autosys?

Events are status changes or triggers that affect job execution. They can be:

System-generated (e.g., job completion, failure, or start time).

• User-generated (e.g., manual job triggers or external signals).

  
  

  
  

  
  

Key Characteristics:

Events determine when a job starts, stops, or retries.

• 
  

  They enable job dependencies (e.g., Job B runs only after Job A succeeds).

  
  

  Used for alerting (e.g., notify admins if a job fails).

  
  

  Types of Events in Autosys:

  
  

  Job Status Events

  
  

  Event	Description
  STARTJOB	Job begins execution.
  SUCCESS	Job completes successfully (exit code 0).
  FAILURE	Job fails (non-zero exit code).
  TERMINATED	Job was manually killed (sendevent -E KILLJOB).
  RESTART	Job is set to retry after failure.

• 
  

  
  

  Dependency Events

  
  

  Used to control job workflows:

  Event	Description
  JOB_SUCCESS	Fires when a dependent job succeeds.
  JOB_FAILURE	Fires when a dependent job fails.
  FILE_ARRIVAL	Triggered when a file appears in a specified path.
  TIME_TRIGGER	Scheduled event (e.g., run_calendar: business_days).

  
  

  
  

  External & Custom Events:

  
  

  Event	Description
  ALARM	Used for notifications (e.g., sendevent -E ALARM).
  USER_EVENT	Custom triggers (e.g., sendevent -E USER_EVENT -P "DATA=value").

  
  
  
  
  How Events Work:
  
  

  Event Flow Example:

  
  

  1. Job A runs and finishes with SUCCESS.

     1. Autosys generates a JOB_SUCCESS event for Job A.

        1. Job B (dependent on Job A) receives the event and starts.

           
           

           
           

           Event-Driven Automation:
           
           
            File watcher:
           
           
           insert_job: FILE_WATCHER

           command: touch /tmp/trigger.file

           condition: FILE_ARRIVAL(/data/incoming/file.txt)

           
           

           Time-Based:

           
           

           insert_job: NIGHTLY_BACKUP

           run_calendar: DAILY

           start_times: "02:00"