How to Create an AutoSys Job Using a JIL File

 How to Create an AutoSys Job Using a JIL File

AutoSys is a popular job scheduling tool that automates complex workflows across various platforms. To create and manage jobs in AutoSys, you use Job Information Language (JIL). JIL files are plain text scripts that define the attributes and behavior of a job. In this article, we will walk you through the process of creating an AutoSys job using a JIL file.

Step 1: Understand the Basics of JIL

Before you start creating a job, it’s important to understand the structure of a JIL file. A JIL script is a collection of attribute-value pairs that define how the job should behave. The key components of a JIL file include:

• Job Name: The unique identifier for the job.
• Job Type: Defines whether the job is a command (cmd) or a box (box).
• Command: The command or script that the job will execute.
• Machine: The server where the job will run.
• Owner: The user account under which the job will execute.
• Schedule Information: The times and dates when the job should run.
• Conditions and Dependencies: Any prerequisites that must be met for the job to start.

Step 2: Write the JIL Script

Let’s create a simple example where we define a job that runs a shell script to back up a database. Here’s what the JIL script might look like:

insert_job: db_backup_job job_type: cmd
command: "/usr/local/bin/db_backup.sh"
machine: prod_server
owner: dbadmin
permission: gx,ge
date_conditions: 1
days_of_week: mo,tu,we,th,fr
start_times: "02:00"
description: "Database backup job"
std_out_file: "/var/log/db_backup.log"
std_err_file: "/var/log/db_backup.err"
alarm_if_fail: 1

Explanation of the Script:

• insert_job: The command to create a new job in AutoSys.
• db_backup_job: The name of the job.
• job_type: Specifies that this is a command job (cmd).
• command: The script that will be executed.
• machine: The name of the server where the job will run.
• owner: The user who owns the job.
• permission: Defines the access permissions (gx: group execute, ge: group edit).
• date_conditions: Indicates that the job is scheduled to run on specific dates or days.
• days_of_week: Specifies that the job should run Monday through Friday.
• start_times: The time the job should start each day.
• description: A brief description of the job.
• std_out_file: The file where standard output will be logged.
• std_err_file: The file where standard errors will be logged.
• alarm_if_fail: Sends an alarm if the job fails.

Step 3: Save the JIL Script

Once you have written the JIL script, save it with a .jil extension, such as db_backup_job.jil. This will be the file you use to create the job in AutoSys.

Step 4: Load the JIL File into AutoSys

To load the JIL file into AutoSys, you will use the jil command in the AutoSys command-line interface (CLI). Here’s how to do it:

1. Log in to the AutoSys CLI: You can access the AutoSys CLI from a terminal or command prompt where AutoSys is installed.

2. Enter JIL Mode: Type jil at the command prompt and press Enter to enter JIL mode.

   
   jil
   

3. Load the JIL File: Use the batch command to load the JIL file:

   
   batch < db_backup_job.jil
   

   This command will execute the JIL script and create the job in AutoSys.

Step 5: Verify the Job

After loading the JIL file, it’s important to verify that the job was created correctly. You can use the autorep command to check the job details:

autorep -j db_backup_job

This command will display the status and attributes of the job. Verify that all the details match what you defined in the JIL file.

Step 6: Test the Job

Before deploying the job in a production environment, you should test it to ensure it behaves as expected. You can manually start the job using the sendevent command:

sendevent -E FORCE_STARTJOB -J db_backup_job

Monitor the job's execution and check the logs to ensure it runs correctly.

Best Practices for Creating AutoSys Jobs

• Use Descriptive Names: Job names should be descriptive enough to indicate their purpose.
• Version Control: Keep track of changes to your JIL scripts using version control systems like Git.
• Testing: Always test jobs in a non-production environment before deploying them to production.
• Documentation: Document the purpose and behavior of each job for future reference.

Conclusion

Creating an AutoSys job using a JIL file is a straightforward process that gives you control over job scheduling and management. By following the steps outlined in this article, you can define, load, and verify jobs in AutoSys with ease. Mastering JIL scripting is key to leveraging the full power of AutoSys in automating and optimizing IT workflows.