Configuration to modify UNIX/Windows user account mapping behavior

You can select a preferred execution domain for a particular job. The execution domain must be included in the LSF_USER_DOMAIN list. When you specify an execution domain, LSF ignores the order of the domains listed in LSF_USER_DOMAIN and runs the job using the specified domain. The environment variable LSF_EXECUTE_DOMAIN, defined in the user environment or from the command line, defines the preferred execution domain. Once you submit a job with an execution domain defined, you cannot change the execution domain for that particular job.

Configuration file

Parameter and syntax

Behavior

.cshrc

.profile

LSF_EXECUTE_DOMAIN=

domain_name

  • Specifies the domain that LSF uses to run jobs on a Windows host

  • If LSF_USER_DOMAIN contains a list of multiple domains, LSF tries the LSF_EXECUTE_DOMAIN first
The following example shows the changed behavior when you define the LSF_EXECUTE_DOMAIN.

When…

In the file …

And the job is submitted by …

The job …

LSF_USER_DOMAIN= SUPPORT:ENGINEERING

and

LSF_EXECUTE_DOMAIN= ENGINEERING

lsf.conf

.profile .cshrc

  • user1 on a UNIX host

  • Runs on a Windows host as ENGINEERING\user1; if the job cannot run with those credentials, runs as SUPPORT\user1

  • Runs on a UNIX host as user1

These additional examples are based on the following conditions:

  • In lsf.conf, LSF_USER_DOMAIN=SALES:ENGINEERING:BUSINESS

  • The user has sufficient permissions to run the job in any of the LSF user domains

UNIX user1 enters …

And LSF_EXECUTE_DOMAIN is …

Then LSF runs the job as …

bsub -m "hostb" myjob

Not defined in the user environment file

SALES\user1

bsub -m "hostb" myjob

Defined as BUSINESS in the user environment file

BUSINESS\user1

setenv LSF_EXECUTE_DOMAIN BUSINESSbsub -m "hostb" myjob

Either defined or not defined in the user environment file

BUSINESS\user1 The command line overrides the user environment file.
Parent topic: UNIX/Windows User Account Mapping