The scheduler file name must be completely and absolutely specified and be given an ".exe" ending on Windows systems. This is because the Job Scheduler requires the complete file name in order to be able to start either a job or itself.

The "-config=" prefix before file names can be omitted.

This option specifies the configuration file or configuration directory. Should a configuration directory be specified, then the Job Scheduler will expect to find the configuration file in the configuration directory, under the name scheduler.xml.

On Unix systems: the Job Scheduler writes its process ID (PID) in this file. This file is deleted by the Job Scheduler on stopping.

See also and .

Note that if a port is blocked, the Job Scheduler will attempt to access it for two minutes before terminating itself.

See also .

See also .

This option should only be used in exceptional situations, as it switches off the test whether or not a port has been set free by the operating system.

Calls setsockopt(socket,SOL_SOCKET,SO_REUSEADDR,true).

This option should only be used in an emergency, should a port be permanently blocked by the operating system although it is no longer used by an application. This can happen with Windows XP, when an application is terminated by a debugger and UNIX can take up to a minute to release a port.

In some situations the Job Scheduler cannot be reached with -reuse-port via TCP or UDP, when the port is being used by other applications. The use of -reuse-port is not recommended.

The Job Scheduler executes xml commands such as immediately on starting.

Specifies the Path/ Name for an alternative factory.ini file.

When references in this documentation are made to the factory.ini file, it should be clear that the value given in this option is meant.

See also

Specifies the Path/ Name for an alternative sos.ini global configuration file. Note that this file contains the Job Scheduler license key.

This option is used when the Job Scheduler is called from a Java class file (for example, when debugging) and jobs are to be started in their own processes.

The Job Scheduler runs in the background on Unix systems , which means that output cannot be written to the terminal.

Under Unix the Job Scheduler stdin, stdout und stderr und directs the output to the scheduler.out file, which must remain writable.

-validate-xml- switches the validation off (should the schema have errors).

See .

-env=NAME=VALUE sets the NAME environment variable.

Requires use of a database - see .

More than one Job Scheduler with the same Scheduler-Id () and the same database can be started with -exclusive. In this case, then only one Job Scheduler will become active. It is only after this active Job Scheduler fails or is stopped (), that another Job Scheduler will become active and take over operation. The takeover takes approximately one minute.

Warning: All participating Job Schedulers must be started -exclusive or . When one Job Scheduler is started with and one without this setting, then two Job Schedulers will run simultaneously, which can lead to unexpected results.

See also .

Only possible in combination with .

A backup Job Scheduler only takes over operation - it cannot start a new operation. This means that after the backup Job Scheduler does not start, but waits for another Job Scheduler to start operation.

-backup is allocated its own service name when used together with and . This means that the backup Job Scheduler can be run on the same computer as the active Job Scheduler as its own service.

The name of the main log file contains the "_backup" suffix.

Only possible in combination with .

When more than one inactive backup Job Schedulers are available to replace a failed Job Scheduler, (), then operation is taken over by the Job Scheduler allocated the lowest value.

Note that it is possible for another Job Scheduler as that dictated by the highest backup-precedence to take over operation, should the backup Job Schedulers run on different computers and should the clocks of these computers not be synchronized,

The default value is 1, when is set, otherwise it is 0.

Requires use of a database (). More than one Job Schedulers can share the execution of orders, when they are all started under the same Scheduler-Id (), use the same database and the same configuration.

allows a job chain to be used for distributed operation.

The default directory is the live directory, which is specified in the ().

The Job Scheduler looks in this directory for jobs, job chains, permanent orders, process classes and locks. 

c:\bin\scheduler.exe c:\scheduler\config.xml -log-dir=c:\scheduler\logs

The Job Scheduler is not started by this option but installed as a Windows service. In this case the following command line options may be specified:









Note that -install-service=name is the same as -install-service -service-name=name.

Removes a service which was previously installed using -install-service.

-remove-service= name is the same as -remove-service -service-name= name.

Only used together with -install-service or -remove-service. When this option is missing but -id=is specified, then the Job Scheduler uses the name sos_scheduler_ scheduler_id. If has been set, then this option adds _backup.

Only used in conjunction with the -install-service. This name is shown by the Windows service controller. It may contain spaces. Should this option not be specified, the Job Scheduler creates a name from the service name (see -service-name=).

Only used together with the -install-service.

This option specifies a service such as a database server which must be running before Windows starts the Job Scheduler. This option must be used in conjunction with the -install-service.

This option can be repeated should the Job Scheduler require a number of services.

The name (or IP number) and port number of the Job Scheduler being addressed.

The name of the temporary job process class -, see .

Script language, see .

Start time - in the form "yyyy-mm-dd HH:MM[:SS]". See .

A job will not be started after its start time has been passed.

The Job Scheduler uses the current time from the computer on which it is running when, for example, starting jobs.

-at=now is the default setting and causes a job to be started immediately.

A temporary job is forwarded to the target Job Scheduler, which is addressed using .

This job only exists until the Job Scheduler is restarted. 

echo ls -l | scheduler -scheduler=localhost:4444 -at="2006-04-04 12:00"

The name of the job chain on which an order is to be run - see .

The order identifier - see .

An order can be given a title. See .

is used to define the Job Scheduler which an order is forwarded to.

The order parameters (see ) can be forwarded to the command line in the form:name=value. 

scheduler -scheduler=localhost:4444 -job-chain=my_job_chain -order-id=123 city=Berlin phone="+4930 864790-0"

This option does not start a Job Scheduler but sends an XML command to another Job Scheduler on the same computer which has the same -tcp-port= option. This can be, for example, : -send-cmd="<terminate/>"

This command is sent to the IP address specified in the attribute or, should this not have been set, to 127.0.0.1.

Stops a Job Scheduler whose process is specified in the file. The Scheduler is stopped using kill -SIGKILL.

Stops the process with the specified PID using kill -SIGKILL. 

scheduler -kill -pid-file=/home/scheduler/scheduler.pid

The Job Scheduler comes with its own XML schema which XML commands and the XML configuration must conform to.

See the Job Scheduler XML Schema.

Expands the Java Class Path, which is specified as a parameter. This means that jokers are processed as .

The Job Scheduler writes the results to stdout. Unless otherwise specified in an option, the Job Scheduler will then terminate itself, without any other output. 

export CLASSPATH="`scheduler -expand-classpath='/opt/java/lib/*.jar'`"

Causes the Job Scheduler to output its version number and date when starting.

Shows the command line options.

Shows the command line options.

The Job Scheduler is started using a straightforward command. 

C:\>…scheduler installation path…\bin\scheduler.exe …\my_scheduler_configuration.xml …
user@host:~>…installation path…/bin/scheduler …/my_scheduler_configuration.xml …

Parameters for the command line operations described here and which are written to the right of the "=" can be set in inverted commas ("") or in apostrophes / single quotes ('').

The Job Scheduler installation program creates the start script - either .\bin\jobscheduler.cmd (Windows) or ./bin/jobscheduler.sh (Unix), in which command line options and environment variables are already set. This script can be modified as required.

Note that the start script and environment variables are described in the »Installation and Configuration« handbook.