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.