Autosys Scheduler Cheatsheet


insert_job: Saves a brand-new job to the database
update_job: PERMANENTLY changes the definition of a pre-
existing job
override_job: TEMPORARILY changes the definition of a pre-
existing job
delete_job: Deletes a single job from the database
delete_box: Deletes a box as well as all the contents


job_type: b, c, f (command is default)
machine: Name of machine (or IP) where job is to be
command: Command to be executed (.exe, .sh, .bat)
watch_file: File being monitored by file watcher
box_name: Used to nest a job inside a box
std_out_file: Redirects output from a command job to a text
std_err_file: Redirects error messages to a text file
condition: Used to structure job dependencies (success,
failure, terminated, done, notrunning, exit code,
and value)
min_run_alarm: Causes job to issue an alarm if it finishes too
max_run_alarm: Causes a job to issue an alarm if it runs too
alarm_if_fail: States whether a job will issue an alarm if it
date_conditions: Toggle which must be set in order for date/time
attributes to be recognized by AutoSys
run_calendar: Specifies the calendar a job will run off of
[cannot be used with days_of_week]
days_of_week: Specifies exact days a job will run [cannot be used with run_calendar]
start_times: Exact time each day a job will run [cannot be
used with start_mins]
start_mins: Minutes after each hour a job will execute
[cannot be used with start_times]
exclude_calendar: Specifies a calendar with days specified upon
which a job will not execute
watch_interval: Steady state for file watchers
watch_file_min_size: Minimum size a file must be before a file watcher
can evaluate to success
box_success: Specifies custom success condition for a box
box_failure: Specifies custom failure condition for a box
max_exit_success: Specifies maximum exit code which will be
evaluated as a success
box_terminator: “If I fail, I kill the box I’m in”
job_terminator: “If the box I’m in fails or gets killed, I kill
term_run_time: “I kill myself after this many minutes”
chk_files: Resource check that verifies a minimum amount
of file space is available before running job
heartbeat_interval: Specifies frequency in minutes at which job’s
command is expected to issue a “heartbeat”
profile: Specifies a file which contains custom
environment variables to be used by a single job
std_in_file: Specifies a file to be used as input for a job
n_retrys: Specifies how many times a job should attempt to
re-run itself after an application-level failure
timezone: Specifies which timezone a job should use when
auto_delete: Specifies how many HOURS after successful
completion a job should delete itself from the
auto_hold: Used only with jobs in boxes. When the box goes
to a RUNNING state, the job will automatically
permission: Extend edit or execute permissions to others
run_window: Specifies when a job can start
avg_runtime: *Only accessible through JIL* Specifies how long
a job takes to run, on average

25 Responses

  1. I currently have autosys submitting jobs to a peoplesoft server residing on one machine. I have now added a second peoplesoft server residing on a different machine. Is there a way to have autosys submit a job to either machine based on the fact that one or the other is down. Basically a failover situation, I can get this to work in peoplesoft manually, but autosys only submits to the first machine and stays queued on peoplesoft side if it’s down. I did notice in the command parms that only the first machine name is entered. Is there a way to put both machine names in so that it checks both servers to see if they are available and sends work to the one that is.

  2. Hi,
    A Box job has 10 command jobs and all are scheduled to run one after another on successful completion. IT fails at the 5th job.
    I want to trigger the box job which will trigger the failed job which is the 5th one and then continue triggering the rest.
    Please let me know how whether this is possible.

Leave a Reply to Gary Cancel reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: