AutoSys Scheduler: Create & Manage Jobs using AutoSys Job Scheduler

AutoSys is used for defining, scheduling and monitoring jobs. These jobs can be a UNIX script, java program or any other program which can be invoked from shell. Before starting we assume that user has already setup an AutoSys environment. This environment consists of autosys server and autosys client.

AutoSys System components

1. Event server (AutoSys database)
2. Event processor
3. Remote agent

Event Server

The event server is a AutoSys database which stores all system information and events as well as all job, monitor, and report definitions. Sometimes this database is also called as a data server, which actually describes a server instance. That is, it is either a UNIX or Windows process, and it is associated data space (or raw disk storage), that can include multiple databases or tablespaces.

Event Processor

This is main component of the autosys system. This processes all the events it reads from dataserver. The event processor is the program, running either as a UNIX process or as a Windows service that actually runs AutoSys. It schedules and starts jobs. When you start the event processor it continually scans the database for events to be processed. When it finds one, it checks whether the event satisfies the starting conditions for any job in the database.

Remote Agent

On a UNIX machine, the remote agent is a temporary process started by the event processor to perform a specific task on a remote (client) machine. On a Windows machine, the remote agent is a Windows service running on a remote (client) machine that is directed by the event processor to perform specific tasks.
The remote agent starts the command specified for a given job, sends running and completion information about a task to the event server, then exits. If the remote agent is unable to transfer the information, it waits and tries again until it can successfully communicate with the database.

Basic functionality of AutoSys

Below is the diagram which explains the basic functionality, please check the explanation.


1. The event processor scans the event server for the next event to process. If no event is ready, the event processor scans again in five seconds.
2. The event processor reads from the event server that an event is ready. If the event is a STARTJOB event, the job definition and attributes are retrieved from the Event Server, including the command and the pointer (full path name on the client machine) to the profile file to be used for the job. In addition, for jobs running on Windows machines, the event processor retrieves from the database the user IDs and passwords required to run the job on the client machine.
3. The event processor processes the event. If the event is a STARTJOB, the event processor attempts to establish a connection with the remote agent on the client machine, and passes the job attributes to the client machine.
The event processor sends a CHANGE_STATUS event marking in the event server that the job is in STARTING state.
4. On a UNIX machine, the inetd invokes the remote agent. On a Windows machine, the remote agent logs onto the machine as the user defined as the job’s owner, using the user IDs and passwords passed to it from the event processor.
5. The remote agent sends an acknowledgment back to the event processor indicating that it has received the job parameters. The socket connection is terminated. At this point, the event processor resumes scanning the event server database, looking for events to process.
6. The remote agent starts a process and executes the command in the job definition.
7. The remote agent issues a CHANGE_STATUS event marking in the event server that the job is in RUNNING state.
8. The client job process runs to completion, then returns an exit code to the remote agent and quits.

Defining autosys job

There are various parameters to define autosys job. Starting from profile, timezone, start time, starting condition and so on. There are the two methods you can use to create job definitions:
1. Using the AutoSys Graphical User Interface (GUI).
2. Using the AutoSys Job Information Language (JIL) through a command-line interface.

In this tutorial we will use JIL language to create autosys jobs.

JIL stands for Job Information Language. Using this you can instruct autosys to save job definitions. This information saved in autosys database. You can also create a jil file which contains job definition. You can then pass this jil file to autosys.

Essential attributes for defining job
1. Job Name
JIL Keyword : insert_job. Name used to identify the job.
2. Job Type
a. JIL Keyword : job_type. The job type is one of job types: command (c), file watcher (f) or box (b).
3. Owner
a. JIL Keyword : owner

The job owner specifies whose user ID the command will be run under on the client machine. This attribute is automatically set to the user who invoked jil or the GUI to define the job, and cannot be changed except by the edit superuser.

Other job attributes:

1. command: The command attribute can be the name of any command, executable, UNIX shell script or batch file, and its arguments.
2. machine: This attribute specifies the client machine on which the command should be run.
3. date_condition: The start date/time dependencies attribute is a toggle, which specifies whether or not there are date, time, or both, conditions required for starting the job.
4. days_of_week: The days of the week attribute specifies the days on which the job should be run.

Sample jil file for command job echoJob.jil

command:echo “Hello this is command job”

To add this job in atosys db. Run following command from unix:

jil < echoJob.jil

This command will add “echoJob” job to autosys databse.

Commands to control the job

Start job command

sendevent –E FORCE_STARTJOB -J <job_name>

sendevent -E STARTJOB -J <job_name>

To put jobs on OFF ICE or ON ICE

sendevent -E OFF_ICE -J <job_name>

sendevent -E ON_ICE -J <job_name>

sendevent -E KILLJOB –J "Job Name Here"

Meaning of AutoSys status

QW QUE_WAIT Queue Wait
RD Refresh Dependencies
RF Refresh Filewatcher


Get our Articles via Email. Enter your email address.

You may also like...


  1. Tinshuk Singh says:

    Is it possible to define time for a job which is inside the box for which time has already defined ? for eg.
    suppose there is a box Box1 which has run time defined as 10:00 and contains two jobs job1 and job2, consider if time for job2 has defined as 12:00.
    can we do like this ?
    if yes then what will be expected behavior?

    • Laxman says:

      We could, but such case we create one more Box with job2 runs at 12:00 clock instead of keeping same box

    • neha says:

      Hi Tinshuk Singh ,

      The Box 1 will kick OFF at 10:00 & the jobs inside the box will wait until its conditions are meet , the job2 will kick off at 12:00

  2. Naresh says:

    Can we able to hold all the job in autosys in the same time.. if yes can u explain how..

    • Laxman says:

      We can HOLD or OFF hold all jobs same time, To hold it you need to create one sendevent job and test file which conatain all jobs with sendevent command.

  3. ABCD says:

    hi guys

  4. Urvashi says:

    Has anyone worked on job dependencies across instances? The one in which we use the caps char “^” to define a condition if a job has dependency on another job in a different instance? Need some help on it.

    Job A on Instance X
    Job B on instance Y
    Condition on job A: s(B^Y)
    Need some info on this

  5. Shubh says:

    Hi Urvashi,

    Job A on Instance X
    Job B on instance Y
    Condition on job A: s(B^Y)

    The above condition is absolutely correct. Please let me know what query do you have..


  6. sushanth says:

    Can we have a condition like ‘not running’ in autosys job
    I have a requirement –> in one of the job the condition should be if previous job doesn’t run at 7pm, then run the present job.

  7. K.Vasanth says:


    Can some one say how to extract active Jobs email id? I know it can be sone through extracting JIL and from there. Is there anyway it can be done directly?

  8. newbie says:


    I get the following error:
    CHASE 09/29/2013 04:13:07 0 PD 09/29/2013 04:13:15

    I have checked the remote agent process and its up and running, I also issued a autosttaus command to see whats the status of the job in the eventsystem,

    can some one please explain why this error occurs and how to fix it.
    I’d appreciate a detail explaination.


  9. newbie says:


    I get the following error:
    CHASE 09/29/2013 04:13:07 0 PD 09/29/2013 04:13:15

    I have checked the remote agent process and its up and running, I also issued an autostatus command to see whats the status of the job in the eventsystem,

    can some one please explain why this error occurs and how to fix it.
    I’d appreciate a detail explaination.
    Also,would like to know how to start a remote agent. I mean,do we need to have a process running on the remote machine where the actual shell script is executed ?


  10. Sowmya says:

    Can we put all the jobs in a box ONICE by just giving the Box name?

  11. Raj Patel says:


    What are best practice server component requirements (CPU, RAM, disk space, etc) we would need to build to efficiently run 5000 simultaneous jobs?


  12. Confused_user says:

    If it possible to set a starting condition below

    RU(JobA) & S(JobB)

    SO basically i want a job to trigger if and only if job A is still in Running and job B is in success

  13. Sneha says:


    I have defined box B1 which has two jobs J1 and J2. If I force start the box B1, the job J1 didn’t run. Both the job status just changed to Activated. But if I force the jobs individual, the job runs successfully. Can anyone please tell me is this because of any configure issue in JIL and which attribute must be included.

    • SamsHaja says:

      Hi Sneha,

      you shouldn’t put any starting time condition like “start_times:” for job “J1” inside the box “B1”

      JIL for box:

      job_name: B1
      job_type: b
      date_condision: 1
      days_of_week: all
      start_times: “10:00”
      timezone: India

      JIL for job J1

      job_name: J1
      job_type: c
      box_name: B1
      command: sleep 100
      permission: wx, mx
      owner: haja
      machine: localhost
      timezone: India

      JIL for job J2

      job_name: J2
      job_type: c
      box_name: B1
      command: sleep 100
      permission: wx, mx
      conditiond: s(J1)
      owner: haja
      machine: localhost
      timezone: India

      • Sneha says:

        Thanks, that helped :)

  14. Arun says:


    We don’t have access to autosys server and we have only GUI access.
    i wanted to know how to create JIL file in autosys server

  15. Pradhan says:

    Need to know if there are classes held for autosys as me and my team would like to learn about autosys, job scheduling and agent installation. So let me know more about it

  16. VIPIN KUmAR says:

    Do we have any simulator for autosys, so that we can practise at home…
    it will be very helpful for me to create jil and do r n d on that…

    Thanks in advanced…

  17. Srinivas Jami says:

    Hi Viral,
    I have a requirement to migrate Windows & Unix jobs to Autosys. May I know the process and steps to implement this migration?

  18. Kumar says:

    We are running a web URL using the autosys jobs. Now we are getting always the success state even though we got errors in the application.

    How can we assign the return code from web application to the autosys job exit code ?

    Am a newbie and didn’t done through the documentation much..

    Any inputs highly appreciated..

  19. Sneha says:


    Is there a way to add a new calendar date using JIL?

  20. Vasu says:


    Is it possible to assign or submit multiple jobs to the multiple instances of remote agent running on client server?


  21. Shivam says:

    Is there any command to check any jobs scheduled date/time?

    • venshh says:

      autorep -j -d

  22. sowmya says:

    Can I use a sendevent command to change a RUNNING filewatcher job to INACTIVE. Will it have an issues at the backgroud?

    • venshh says:

      you can put as inactive but job will be running in back ground

  23. diana tavolario says:

    If a job is in a RUNNING status, if it is put ON ICE, will the job complete then go into the on-ice status? Also, if the job is a .bat file and runs on another machine… so autosys shows status of SUCCESS, but the job is still running on another server, if put on ice at that point, will job in background continue running?

  24. Venu says:

    Hello All,
    I am a new bee in DEVOPS. I have limited knowldge about autosys. I am looking at automating the job to put on ON ICE, ON OFF state from an external tool which is runnng on unix m/c. I came to know there is a JIL language to do this. can any one help me how to script this and test ? It would be great if there is any sample code for this.

    Thanks in advance.

  25. Jaya says:

    Hi, I am a beginner and keen to learn Autosys, Could you pls guide me where should I practice Autosys commands? Is there a unix or windows server for practice?

  26. Vechoorian says:


    can any one help me to launch autosys GUI from unix server

  27. Toroop says:

    Where to download autosys software from .

  28. Peter says:

    How can I move a box from test autosys into production autosys using JIL?

    • jagadeesh says:

      change the machine name , instead of autosys(test) to Prod Autosys.then insert the jil into prod server.

  29. Hi
    Could you please list out the GUI availble to connect to autosys . as I am using Humming bird excced tool till now. But from 1 month i am unable to connect to Hummin bird excced . Please help me

  30. aaditya says:

    Is Autosys having any Java API ? If yes then can you please point me to it ?


  31. amit says:

    is it possible to make a script through which ticket gets auto resolved once the job is marked to success?? if yes, please help

  32. preity says:

    Will a job which is not part of any box job go to Activated state if the starting conditions are not met? Suppose a job A has start time: 4:00, and also dependency on success of Job B. At 4:00, Job B is still running, will the Job A go to activated state or it will remain in SU status(of previous day’s run).

    • venshh says:

      it will be active state only and waiting for job b to get complete

  33. Kiran says:


    We have some scheduled Job’s in AutoSys. As and when the command got executed it is returning sucess even though the script returned some errors. Is there any way in AutoSys to put the return code based on the execution of the script…Please help me..

  34. Pritam Dey says:

    How to practice Autosys in Home Environment..??

  35. mayur says:

    I need to create a command job which will run on weekend only if weekend appears on monthend

  36. Dao Shi says:

    Can one set a limit on how many concurrent jobs within a box be run? I have more than 100 jobs within a box, they don’t have dependency among each other. The problem is that our system cannot handle too many concurrent jobs at once, so I need to put a limit of the number of the jobs run within the box.

    Cannot find any information for this from the manual.

  37. gajendra says:

    Could you please assist me to debug the issue, shell script has the nohup java classname &.
    If it is executed manually it create java process but it is executed from autosys it does not create java process.
    echo path and class path in both ways but it is same. Please what are all other possible ways.

  38. venkat says:

    we installed autosys on a windows machine. i am able to generate the job statistics report from the autosys console. but i need it from the command line. i tried autorep command, but it is giving the report for a particular job or for a particular pattern of the job. i need the report for all the jobs.

Leave a Reply

Your email address will not be published. Required fields are marked *