This section explains some of the basic concepts and terminology associated with using Job Scheduler.
A job is a series of one or more actions performed on a database in a single operation, such as backing up, updating statistics, and dumping a database.
A schedule defines a timescale for how and when jobs are executed and re-executed.
A scheduled job is a job that has been bound to a schedule. Only scheduled jobs are executed.
The Job Scheduler Task (JS Task) is the functional component responsible for managing the schedules and providing timely notification to the Job Scheduler Agent to execute a particular job.
The Job Scheduler Agent (JS Agent) is the functional component responsible for executing a job when notified by the JS Task.
A repeating schedule is a schedule that is active more than once. All repeating schedules must have both start and end times.
A target server is the Adaptive Server on which a job is scheduled to run.
A template is a set of Transact-SQL (T-SQL) statements with parameters that can be used to create a job within the Job Scheduler.
JS Task wakes up on demand, either by a job scheduled to be run or by a wake-up event that has occurred, such as the creation of a new job. At regular intervals (configurable by the database administrator), JS Task scans the sybmgmtdb database tables and collects applicable schedule information to maintain its dedicated server tables js_callouts and js_history. The JS Task performs the functions that allows Job Scheduler to perform its internal tasks. It is also what makes Job Scheduler run time programmable within ASE.
