AUTOSYS TUTORIALS Autosys Quick Reference. Introduction to Autosys. Auto. Sys is an automated job control system for scheduling, monitoring, and reporting. These jobs can reside on any Auto. Raise Your Game Synonym on this page. Sys configured machine that is attached to a network. An Auto. Sys job is any single command, executable, script, or Windows batch file. Each Auto. Sys job definition contains a variety of qualifying attributes, including the conditions specifying when and where a job should be run. Defining Jobs There are the two methods you can use to create job definitions Using the Auto. Sys Graphical User Interface GUI. Using the Auto. As per the Autosys manual, the following permission options can be configured in the JIL file gx,ge,wx,we,mx,me Can someone please explain what each of these options. Highly recommended Autosys interview questions and answers by Aptibook. The section contains many frequently asked questions on jobs and scheduling mechanisms and all. CA+Workload+Automation+AE+Components.png' alt='Autosys For Windows' title='Autosys For Windows' />Sys Job Information Language JIL through a command line interface. Autosys Jobs Job Types and Structure There are three types of jobs command, file watcher, and box. As their names imply, command jobs execute commands, box jobs are containers that hold other jobs including other boxes, and file watcher jobs watch for the arrival of a specified file. In the Auto. Sys environment, the box job or box is a container of other jobs. A box job can be used to organize and control process flow. The box itself performs no actions, although it can trigger other jobs to run. SiteAssets/TEC1038064_Embeded/ss1.PNG' alt='Autosys For Windows' title='Autosys For Windows' />An important feature of this type of job is that boxes can be put inside of other boxes. Default Box Job Behavior Some important rules to remember about boxes are Jobs run only once per box execution. Jobs in a box will start only if the box itself is running. As long as any job in a box is running, the box remains in RUNNING state the box cannot complete until all jobs have run. By default, a box will return a status of SUCCESS only when all the jobs in the box have run and the status of all the jobs is success. By default, a box will return a status of FAILURE only when all jobs in the box have run and the status of one or more of the jobs is failure. Unless otherwise specified, a box will run indefinitely until it reaches a status of SUCCESS or FAILURE. Changing the state of a box to INACTIVE via the sendevent command changes the state of all the jobs in the box to INACTIVE. Job States and Status Auto. Sys keeps track of the current state, or status, of every job. The value of a jobs status is used to determine when to start other jobs that are dependent on the job. The job status is displayed in the job report generated by the autorep command, and in the job report you can view in the Job Activity Console. Following are the status of Autosys jobs INACTIVE The job has not yet been processed. Either the job has never been run, or its status was intentionally altered to turn off its previous completion status. ACTIVATED The top level box that this job is in is now in the RUNNING state, but the job itself has not started yet. STARTING The event processor has initiated the start job procedure with the Remote Agent. RUNNING The job is running. If the job is a box job, this value simply means that the jobs within the box may be started other conditions permitting. If it is a command or file watcher job, the value means that the process is actually running on the remote machine. SUCCESS The job exited with an exit code equal to or less than the maximum exit code for success. By default, only the exit code 0 is interpreted as success. If the job is a box job, this value means that all the jobs within the box have finished with the status SUCCESS the default, or the Exit Condition for Box Success evaluated to true. FAILURE The job exited with an exit code greater than the maximum exit code for success. By default, any number greater than zero is interpreted as failure. Auto. Sys issues an alarm if a job fails. TERMINATED The job terminated while in the RUNNING state. A job can be terminated if a user sends a KILLJOB event or if it was defined to terminate if the box it is in failed. If the job itself fails, it has a FAILURE status, not a TERMINATED status. A job may also be terminated if it has exceeded the maximum run time termruntime attribute, if one was specified for the job, or if it was killed from the command line through a UNIX kill command. Auto. Sys issues an alarm if a job is terminated. RESTART The job was unable to start due to hardware or application problems, and has been scheduled to restart. QUEWAIT The job can logically run that is, all the starting conditions have been met, but there are not enough machine resources available. ONHOLD This job is on hold and will not be run until it receives the JOBOFFHOLD event. ONICE This job is removed from all conditions and logic, but is still defined to Auto. Sys. Operationally, this condition is like deactivating the job. It will remain on ice until it receives the JOBOFFICE event. The difference between on hold and on ice is that when an on hold job is taken off hold, if its starting conditions are already satisfied, it will be scheduled to run, and it will run. On the other hand, if an on ice job is taken off ice, it will not start, even if its starting conditions are already satisfied. This job will not run until its starting conditions reoccur. The other major distinction is that jobs downstream from the job that is on ice will run as though the job succeeded. Whereas, all dependent jobs do not run when a job is on on holdnothing downstream from this job will run. Starting Parameters Auto. Sys determines whether to start or not to start a job based on the evaluation of the starting conditions or starting parameters defined for the job. These conditions can be one or more of the following Date and time scheduling parameters are met it is or has passed the specified date and time. Starting Conditions specified in the job definition evaluate to true. For jobs in a box, the box must be in the RUNNING state. The current status of the job is not ONHOLD or ONICE. Every time an event changes any of the above conditions, Auto. Sys finds all the jobs that may be affected by this change, and determines whether or not to start them. Oasis Software. Writing jil code insertjob template jobtype cboxname box. TANT A0. 1permission gx,ge,wx,we,mx,medateconditions 1daysofweek allstarttimes 1. Explanation of each line Insertjob this will let the autosys server to recognize the job and inserts into autosys Data. Base. Jobtype there are two types of jobs namely box and child cchild, boxboxname this is the box job name box job can have more than 1 child jobs. Error log file if the job failsminrunalarm if the job terminatescompleted with in that time it generate an alarmmaxrunalarm if the job runs for more than the specified time, it generate an alarmalarmiffail generates an alarm if the job failsprofile the file where you can keep all your variables variable namesWe dont use all the above options in all the jobs, it depends on the requirements. Here is a sample job which will verify a particular process is running or not. SAPUATMU0. C insertjob SAPUATMU0. C jobtype ccommand localSAPprocess. Check. UAT. shmachine MU0. UATowner adminMU0. UATpermission gx,wx,mx,medaysofweek allstarttimes 1. Job used for Run testing of processalarmiffail 1maxexitsuccess 1. To Insert a new JIL code issue command jilbash 3. The following prompt will appear copy paste the jil code u have made example of jil code below. At the end the C or B determines if the job is box job or child job. Using Autorep command Function.