The Job Scheduler can be used either with or without a database. Operation with a database has the following advantages:

Task Queue

The Job Scheduler stores all queued tasks in a table under its scheduler ID (Option ). When the Job Scheduler restarts, then all queued tasks are reread from the database.

Orders

The Job Scheduler saves every order in a database table with the scheduler ID (Option ). When the Job Scheduler restarts, it rereads the orders from the database.

Task History

The Job Scheduler records information about every task performed, apart from the Job Scheduler start and stop.

Instruction History

The Job Scheduler records the course of every operation in the job stream in the instruction history.

Further information about the instruction history can be found here: Job History.

The creation of the database tables is described in .

Settings

Database and Error Handling

Table Names

Should a History be Written?

Should Protocols be Included in the History?

The Addition of Custom Columns in the Task History

The Conditions for an Entry in the Task History

Application Programming Interface

The spooler object initializes table names

Describe history fields ()

Commands

Show History

Command
Command
Command

Error-Tolerance

The Job Scheduler tolerates database errors and can carry out routine operations with a temporarily unavailable database. More detailed information can be found in .

The Job Scheduler can be set to wait for a reconnection in the event of loss of contact with the database. In this situation, only commands other than TCP or HTTP are processed; The Job Scheduler cannot be shut down, only terminated (see Termination).