Autosys FAQ Summary

System component working principle and brief descriptionSystem Components: Event Server, event processor, remote proxy
Event processor requests (1) relevant job information obtained after the event server (2) and passed it through proxy connection (3) to remote proxy (4 ), the Remote Agent sends a receipt to the event processor, indicating that the task content has been received (5 ). Then, the remote proxy starts RUNNING the client job (6) and initiates a CHANGE_STATUS event to notify the Event Server job status to RUNNING (7). When the client job is completed, the remote proxy (8) send the program end status code (9) to the Event Server ).

The figure is from the watermark.

Common job typesCommand-It can be a shell script or an executable program.
Box-As a container that can contain other jobs, it can organize and control the processing process. If the running conditions are not specified for the jobs in the Box, the jobs in the Box will run concurrently when the Box meets the running conditions.
File watcher-Start a file monitoring process to check whether a file exists and the file size. When the File size reaches a minimum detection value and does not continue to grow, the File Watcher job is successfully executed.

Common OperationsAutorep-> List information about a specified job.-> autorep-j <JOB_NAME>
Job_depends-> View dependency conditions-> job_depends [-c |-d] [-J job_name]
Sendevent-> Job control-> sendevent-j <JOBNAME>-e <EVENT>
Description of available EVENT values
+ STARTJOB-start a job
+ FORCE_STARTJOB-Force start of a job without considering its dependency conditions and scheduling settings
+ KILLJOB-close a job
+ DELETEJOB-delete a job
+ JOB_ON_ICE-like the ON_HOLD below, ON_ICE will also prevent the specified job from running. The differences are as follows:
+ JOB_OFF_ICE-opposite to ON_ICE operations
+ JOB_ON_HOLD-stops the specified job from running
+ JOB_OFF_HOLD-opposite to the ON_HOLD operation
+ CHANGE_STATUS-manually repaired the job status. This function can be used when Autosys cannot track the job status. For example, in Autosys, it is reported that a job is still running and the job is not running at the time, then, you can run the "sendevent-j <JOB>-e CHANGE_STATUS-s STATUS" command to modify the job status. The STATUS can be ACTIVATED, FAILURE, INACTIVE, ON_HOLD, ON_ICE, QUE_WAIT, REFRESH_DEPENDENCIES, REFRESH_FILEWATCHER, RESTART, RUNNING, STARTING, SUCCESS, or TERMINATED.

Differences between on ice and on hold: 1. For an ON_HOLD job, if the running conditions have been met during ON_HOLD, the job will be executed immediately after OFF_HOLD. In the same case, it is not applicable to jobs after OFF_ICE. Jobs after OFF_ICE must run only after the running conditions are met again.
Difference 2: tasks dependent on ON_HOLD jobs do not run, but those dependent on ON_ICE jobs run. In this case, the status of ON_ICE jobs is considered as SUCCESS.

The final state of a Box job depends on the internal jobs it contains. Only when all the included jobs run successfully, its status is successful. Otherwise, any of the included jobs fails to run, the status changes to failed. When defining a Box job, you do not need to specify the machine name. The machine name is mainly used to run scripts and commands. A Box job is only a job container that has nothing to do with the actually executed process, therefore, the machine name is not required for the Box job.

Reference http://viralpatel.net/blogs/autosys-create-manage-jobs-autosys-scheduler-job-monitoring-autosys/
Http://www.directutor.com/content/autosys-job-handling
Http://pmckinstry.wikidot.com/autosyscheatsheet
Http://javarevisited.blogspot.com/2013/08/difference-between-on-hold-and-on-ice-jobs-autosys-interview-question.html
Http://www.aptibook.com/Technical/Autosys-concepts-interview-questions
Http://supportconnectw.ca.com/public/autosys/infodocs/autosys_cheatsheet.asp
Https://supportcontent.ca.com/cadocs/0/CA%20Workload%20Automation%20AE%2011%203%206-ENU/Bookshelf.html