25.06.2015 Views

Administering Platform LSF - SAS

Administering Platform LSF - SAS

Administering Platform LSF - SAS

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Controlling Execution Environment Using Job Starters<br />

Controlling Execution Environment Using Job Starters<br />

In some cases, using bsub -L does not result in correct environment settings<br />

on the execution host. <strong>LSF</strong> provides the following two job starters:<br />

◆ preservestarter—preserves the default environment of the execution<br />

host. It does not include any submission host settings.<br />

◆ augmentstarter—augments the default user environment of the<br />

execution host by adding settings from the submission host that are not<br />

already defined on the execution host<br />

bsub -L cannot be used for a Windows execution host.<br />

Where the job starter executables are located<br />

Source code for<br />

the job starters<br />

By default, the job starter executables are installed in <strong>LSF</strong>_BINDIR. If you prefer<br />

to store them elsewhere, make sure they are in a directory that is included in<br />

the default PATH on the execution host.<br />

For example:<br />

◆ On Windows, put the job starter under %WINDIR%.<br />

◆ On UNIX, put the job starter under $HOME/bin.<br />

The source code for the job starters is installed in <strong>LSF</strong>_MISC/examples.<br />

Adding to the initial login environment<br />

Example<br />

By default, the preservestarter job starter preserves the environment that<br />

RES establishes on the execution host, and establishes an initial login<br />

environment for the user with the following variables from the user’s login<br />

environment on the execution host:<br />

◆ HOME<br />

◆ USER<br />

◆ SHELL<br />

◆ LOGNAME<br />

Any additional environment variables that exist in the user’s login environment<br />

on the submission host must be added to the job starter source code.<br />

A user’s .login script on the submission host contains the following setting:<br />

if ($TERM != "xterm") then<br />

set TERM=`tset - -Q -m 'switch:?vt100' ....<br />

else<br />

stty -tabs<br />

endif<br />

The TERM environment variable must also be included in the environment on<br />

the execution host for login to succeed. If it is missing in the job starter, the<br />

login fails, the job starter may fail as well. If the job starter can continue with<br />

only the initial environment settings, the job may execute correctly, but this is<br />

not likely.<br />

378<br />

<strong>Administering</strong> <strong>Platform</strong> <strong>LSF</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!