What Are AutoSys Jobs

AutoSys is a job scheduling tool used to automate, monitor, and manage processes across different platforms. It enables the automation of various tasks such as running scripts, executing programs, transferring files, and more. AutoSys jobs are the core entities within AutoSys, which define the work that needs to be performed.

### Types of AutoSys Jobs

There are several types of AutoSys jobs, each serving different purposes depending on the task to be automated. The key types of jobs in AutoSys include:

1. **Command Job**: This type of job executes a command or a script on a specific machine. It can be used to run shell scripts, batch files, or any executable program.

   **Example**:

   ```JIL

   insert_job: my_command_job

   job_type: c

   command: /path/to/my_script.sh

   machine: my_server

   ```

2. **Box Job**: A box is a container for multiple jobs. It allows jobs to be grouped together and can be used to define dependencies between jobs within the same box. A box can contain any number of jobs and will run them in a specified order or based on conditions.

   **Example**:

   ```JIL

   insert_job: my_box

   job_type: b

   ```

3. **File Watcher Job**: This job type waits for a file to appear or change before proceeding with other jobs. It is used when certain tasks depend on the presence of specific files.

   **Example**:

   ```JIL

   insert_job: file_watcher_job

   job_type: f

   watch_file: /path/to/file.txt

   ```

4. **FTP Job**: This job type handles file transfers via FTP or SFTP protocols. It is used to automate data transfers between machines.

   **Example**:

   ```JIL

   insert_job: ftp_job

   job_type: FTP

   source_file: /path/to/source/file.txt

   destination_file: /path/to/destination/

   ```

5. **Database Job**: This job interacts with databases to run SQL queries or perform other database operations.

   **Example**:

   ```JIL

   insert_job: my_db_job

   job_type: d

   command: "SELECT * FROM my_table"

   database_connection: my_db_connection

   ```

### Key AutoSys Job Components

- **Job Name**: Each job must have a unique name that identifies it in the AutoSys system.

- **Job Type**: Specifies the type of job (e.g., command, box, file watcher).

- **Machine**: The server or machine where the job will run. This can be a specific host or a virtual machine in a cloud environment.

- **Command**: The command or script that the job will execute.

- **Dependencies**: Jobs can be dependent on other jobs, meaning they will only run if the preceding jobs have succeeded or reached a certain state.

- **Run Conditions**: Jobs can be scheduled to run at specific times or triggered based on conditions, such as the existence of a file or the completion of another job.

### AutoSys Job Statuses

Each AutoSys job goes through different statuses during its life cycle. Here are some common statuses:

- **STARTING**: The job is in the process of starting.

- **RUNNING**: The job is currently executing.

- **SUCCESS**: The job completed successfully.

- **FAILURE**: The job encountered an error and failed to complete.

- **ON_HOLD**: The job is on hold and will not run until released.

- **TERMINATED**: The job was manually stopped or terminated due to an issue.

- **INACTIVE**: The job is not scheduled to run.

- **ON_ICE**: The job is put on hold, but unlike 'ON_HOLD,' it does not affect downstream jobs.

### Scheduling AutoSys Jobs

AutoSys provides flexible scheduling options for jobs. Jobs can be scheduled to run at specific times, intervals, or based on complex conditions. The most common scheduling attributes include:

- **start_times**: Defines the exact time(s) the job should run.

- **run_window**: Specifies a time range within which the job can start.

- **days_of_week**: Restricts the job to run only on specific days (e.g., Monday to Friday).

- **condition**: Sets conditions for running the job based on the status of other jobs.

### Example JIL (Job Information Language) for a Command Job

Here’s an example of a basic AutoSys command job written in JIL:

```JIL

insert_job: my_job_name

job_type: c

machine: my_machine

command: /path/to/script.sh

owner: user@domain

start_times: "02:00"

days_of_week: mo,tu,we,th,fr

condition: success(my_previous_job)

description: "This job runs a script every weekday at 2 AM."

```

### Monitoring AutoSys Jobs

AutoSys offers tools to monitor and control job execution. Some common commands include:

- **`autorep`**: Displays the current status of jobs.

- **`sendevent`**: Sends events to change the state of a job, such as starting, stopping, or putting it on hold.

  

  **Example**:

  ```bash

  sendevent -E FORCE_STARTJOB -J my_job_name

  ```

### Conclusion

AutoSys jobs are an essential part of automating tasks across systems. With the flexibility to define different job types, set dependencies, and create complex schedules, AutoSys provides an efficient solution for managing enterprise-level workflows. By using jobs to automate tasks, organizations can improve efficiency, reduce manual effort, and ensure reliability in their operations.