##### Page tree
Go to start of banner

# How to add environment variables for all jobs

## Using Command Line Options

• The command line option `-env=[var_name]=[var_value] `adds an environment variable to the JobScheduler.
• This variable only exists in the scope of the JobScheduler.
• If a variable [`var_name]` already exists in the user environment then the value of the `-env` option will become effective.
• The Windows Service of the JobScheduler reads the system and user environment only if it runs in the corresponding user account.
• Environment variables are considered for substitution when used in settings (see Job Scheduler Reference Documentation).

## Start Script with -env

Example for starting the JobScheduler with an environment variable:

## Environment Variables Script: jobscheduler_environment_variables.(sh|cmd)

The JobScheduler start script reads the environment from the .\user_bin\jobscheduler_environment_variables.(sh|cmd) script.

• You will find an example in ./user_bin/jobscheduler_environment_variables.(sh|cmd)-example.
• Rename this file to ./user_bin/jobscheduler_environment_variables.(sh|cmd) to make it effective.
• For Unix make sure that ./user_bin/jobscheduler_environment_variables.sh is readable and executable.
• Edit ./user_bin/jobscheduler_environment_variables.(sh|cmd) if you always want to start the JobScheduler with additional environment variables. If you want to start the JobScheduler Windows service with the `-env` option then a reinstall is required (see below).

Example snippet of [install_path]/user_bin/jobscheduler_environment_variables.(sh|cmd) for adding an environment variable:

## Windows Service

The Windows Service always starts JobScheduler with the options and environment variables that have been used for installation. During the Windows JobScheduler setup a Windows Service is installed that has to be re-installed in order to make new environment variables effective.

For this:

• stop the JobScheduler if it is running:
• remove the JobScheduler service:
• install the JobScheduler service with `-env` option or edit the jobscheduler_environment_variables.cmd file as stated above
• start the JobScheduler service: