Working with JIL in AutoSys

 Understanding Job Information Language for Job Definitions and Automation

AutoSys is a robust workload automation tool used to define, schedule, and manage jobs across distributed systems. At the heart of AutoSys job creation and control is JIL (Job Information Language) — the scripting language that tells AutoSys what jobs to create, modify or remove and how they should behave.

---

What is JIL?

JIL (Job Information Language) is the language used to define AutoSys objects such as:

• Jobs

• Machines

• Global variables

• Job types

• External instances

• Blobs (large binary objects)

• Resources

All of these definitions are interpreted by AutoSys and stored in its database for execution according to set rules and schedules.

---

The jil Command

To work with JIL you use the jil command — the language processor that interprets JIL statements and loads definitions into the AutoSys database.

There are two main ways to use JIL:

📌 1. Interactive Mode

Run jil at the command prompt and enter JIL commands line by line. AutoSys interprets and loads each definition after you exit the prompt.

📌 2. Script Mode

Write all JIL commands in a text file and then use the command:

jil < filename.txt

This method loads all definitions from the script into the AutoSys database at once.

---

Common JIL Subcommands

JIL uses specific subcommands to define and manipulate objects in AutoSys:

🔹 Job-Related Subcommands

• insert_job – Add a new job definition

• update_job – Modify an existing job

• delete_job – Remove a job from the database

• override_job – Temporary change for the next run only

These let you create, modify, or clean up jobs in your automation environment.

🔹 Machine Subcommands

Machines must be defined before jobs can use them:

• insert_machine – Add a machine

• update_machine – Change machine settings

• delete_machine – Remove a machine definition

🔹 Other Object Subcommands

JIL also supports operations for:

• Monitors and reports

• Job types

• External instances

• Blobs and globs

• Resources

Each object type has corresponding insert_, update_, and delete_ subcommands.

---

JIL Script Structure and Syntax

A JIL script is made up of one or more:

• Subcommands — such as insert_job

• Attribute statements — defining properties like machine name, schedule, owner, etc.

Rules for a valid JIL script include:
✔ Each command must follow the subcommand:object_name format
✔ Attribute statements follow the subcommand
✔ Scripts must obey syntax rules (for example, correctly formatted times and values)
✔ Quotes and escape characters may be required for values containing special characters

Using the correct syntax ensures JIL definitions are correctly interpreted and committed to the database rather than being rejected due to errors.

---

Why JIL Matters

JIL provides maximum control and flexibility when defining AutoSys jobs. While graphical interfaces can simplify job creation, JIL is the foundational method that automation experts use to:

• Precisely specify job behavior

• Set dependencies and conditions

• Automate large numbers of jobs via scripts

• Modify jobs efficiently in batch processes

It also integrates with operating system tools, making it ideal for automation on both UNIX/Linux and Windows platforms.

---

Conclusion

Working with JIL is essential for effective AutoSys automation. Through the jil command and carefully structured scripts, administrators and schedulers can define complex workloads that run reliably and efficiently — supporting enterprise workload needs and ensuring tasks execute exactly when and how they should.

Introduction to AutoSys — A Beginner’s Guide

 

Introduction to AutoSys — A Beginner’s Guide

AutoSys is a powerful automated job control and scheduling system that helps IT teams schedule, monitor, and manage workloads across different platforms and environments. It’s widely used by schedulers, operators, and developers who need to run batch jobs reliably and efficiently across servers in enterprise environments.

---

What is AutoSys?

AutoSys is a workload automation tool that allows users to define jobs, set schedules, and control the execution of tasks on remote machines. A job in AutoSys can be any action such as a script, command, executable, or batch file that needs to run at a defined time or based on specific conditions.

Unlike traditional schedulers, AutoSys offers:

• Centralized control of job workflows across distributed systems

• Event-based automation where jobs can trigger based on other job outcomes

• Monitoring and alerting to track job execution and handle failures efficiently

• Support for many platforms including UNIX, Linux, Windows, and enterprise systems like SAP and z/OS.

---

Who Should Use AutoSys?

This guide is especially helpful for:

• Schedulers and operators who define, monitor, and control workload automation

• Application developers who build systems integrating with AutoSys

• System administrators managing distributed batch processing

• IT teams handling complex workflows or mission-critical jobs.

To use AutoSys effectively, you should be familiar with the operating systems and technologies where the jobs will run, such as UNIX/Linux or Windows environments.

---

Key Concepts in AutoSys

Jobs and Job Definitions

In AutoSys, a job is any task you want to automate. Each job has a job definition containing attributes that describe:

• What to run (script, command, executable)

• Where to run (machine/server)

• When to run (schedule or conditions)

• How to run (dependencies, notifications)
  These definitions help the AutoSys scheduler determine how and when to execute the work.

Automated Job Control

AutoSys is event-driven: it monitors events and decides when to initiate jobs. Events can be:

• Scheduled times

• Completion of other jobs

• File triggers or system conditions

When all required conditions are met, AutoSys triggers the job and tracks its status until completion.

---

Agents and Extensions

To execute jobs on remote systems, AutoSys uses agents. These are small software components installed on machines where jobs run. Agents enable AutoSys to:

• Execute scripts and commands

• Transfer files

• Monitor files and processes

• Work with databases or application servers

You can also enhance agent capabilities by installing agent plug-ins that add specialized functionalities such as database monitoring or advanced file handling.

Modern AutoSys versions replaced older remote agents with more capable Workload Automation Agents that support additional job types and platforms.

---

Events, Alarms, and Utilities

AutoSys uses events to drive automation. For example:

• A scheduled time event might trigger a data backup job.

• A dependency event might start a follow-up job only after another finishes successfully.

Alarms are special notifications that alert operators when jobs fail or require attention. Operators can intervene manually using commands like sendevent to resolve issues or restart jobs.

AutoSys also provides a suite of utilities to manage, monitor, and troubleshoot jobs. These include tools for defining jobs (via JIL), checking job status, sending events, archiving logs, and controlling system components.

---

Why AutoSys Matters

AutoSys simplifies complex workload automation needs by centralizing job scheduling and monitoring across heterogeneous systems. It helps organizations:

• Improve operational efficiency

• Reduce manual intervention

• Ensure timely execution of critical tasks

• Maintain visibility over distributed job flows

Because it supports flexible scheduling, dependencies, and automation at scale, AutoSys is a preferred choice for enterprise environments that require robust and reliable workload control.