Three major components of Autosys:
1) Event Server: Database (Syabase/Oracle)
2) Scheduler: Communicate in between, continously scan for jobs
3) Remote agent: Job actually runs here
Default instance: ACE
Autosys is event driven
Manually events are generated using the dendevent command
Why Autosys?
-To automate any process to make business easy
-To reduce manual intervention
-To deliver required results in time
Events:
-To take action on a job
-Action on job is performed using sendevent
-Autosys is completely event-driven, i.e, job is activated by Event Processor
SendEvent:
-Starting or stopping a job
-Putting a job on hold
-Set global variables
-Cancel scheduled events
WorkFlow:
Event
>
Find jobs dependent on this event
>
Check conditions
>
Starting
>
Running
>
Inspects Exit Code of the process
>
Success (returns 1) OR Failure (returns some other code)
SendEvent via command line:
sendevent -E START_JOB -J <Job name>
sendevent -E FORCE_STARTJOB -J <Job name> (ignores date and time consitions)
sendevent -E KILLJOB -J <job name> (kills the process id of the job)
sendevent -E DELETEJOB -J <job name> (deletes the job, if jobs are a box job, then all the jobs are deleted)
sendevent -E JOB_ON_HOLD -J <Job name>
sendevent -E JOB_OFF_HOLD -J <Job name> (job starts executing right after it is put off-hold)
In this section no one knows what actually works behind the triggered job in analysis
for every even or odd terms of the sequence numbers as given by the same socket for the third or fourth routine
including the duration symbolization of the copy set of the same and continue transfering the same event
event loop:
-Event loop keeps on continued until all of them have been revised and created
-Continued procedures untill they're finished in the same scheduled tasks
-Orthorized continued version ofr every XML files and their assigments for the same files
-Intext changing continuation of the
sendevent -E JOB_ON_ICE <job name>
sendevent -E JOB_OF_ICE -J <Job name>
