Juniper MEDIA FLOW MANAGER 2.0.2 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual page 125

Media Flow Manager Administrator's Guide
Jobs are specified in local time, meaning that if the time on the system changes, the job
occurs in the new local time of the system (assuming that time has not passed).
An arbitrary number of CLI commands may be specified with a job and are executed in the
order specified by the set sequence numbers. If a command in the sequence fails, no further
commands in the job are executed (unless fail-continue is set). The error message (if any)
associated with the job execution reflects the failure of only the last command attempted
(which is either the command that failed first if fail-continue is not set, or the last command
that produced an error if fail-continue is set).
No two jobs are allowed to run at the same time (i.e. overlap execution). If it comes time for job
B to execute while job A is still executing, job B is rescheduled for a short distance in the future
(1 second) continually until job A is finished. Each command failure associated with a job is
logged to syslog.
If the scheduler is restarted, all previous job state is lost and a previously executed job that
was in the completed state, is now in the inactive state and all results are empty.
All jobs are executed implicitly in the context of enable and configure terminal (Configure
mode).
job <job_ID> [enable | execute | fail-continue | name <name>]
command <sequence_#> <command_string>
comment <comment_string>
schedule
daily time <hh>:<mm>:<ss>
monthly [day-of-month <day>] [interval <months>] [time <hh>:<mm>:<ss>]
once time <hh>:<mm>:<ss> date <yyyy>/<mm>/<dd>
periodic interval <interval_time>
type {once | daily | weekly | monthly | periodic}
weekly {day-of-week <day> | time <hh>:<mm>:<ss>}
Create a job by entering a job identifier (job_ID), command string, and sequence#, and
enable the job (if a job is disabled, the default, it does not execute automatically according to
its schedule; nor can it be executed manually), execute, set fail-continue (continue executing
commands when one fails), or name the job. Use no job <job_ID> <option> to reset or
delete. Notes:
•
command
•
command_string
•
sequence#
relative to other commands in this job; jobs are executed in ascending order.
•
comment
•
schedule
job. Once the parameters are set, they remain so whether used or not. Default is once.
•
daily
no to reset it the default, which is midnight.
•
monthly
•
•
—Add a CLI command to the job. Enter as many commands as needed.
—The CLI command.
—An integer that controls the order in which the command is executed
—A string that displays with show job <job_ID>.
—Set scheduling parameters and then implement them by setting a type for the
—Set the time of day at which a schedule type daily executes every day; use
—Set parameters for the schedule type monthly:
—Set which day a schedule type monthly executes: a number
day-of-month
from 1 - 28 (29-31 not allowed as these days do not exist in every month). Use no
to reset the default, 1.
—Set the number of months between executions of a monthly job;
interval
default is 1, which is the only setting that makes the job truly "monthly." 2 means
CHAPTER 5 CLI Commands
job 125