UNIX/Windows user account mapping behavior

The following examples describe how UNIX/Windows user account mapping enables job submission and execution across a mixed UNIX/Windows cluster.

When…	In the file …	And the job is submitted by …	The job …
UNIX/Windows user account mapping is not enabled	—	BUSINESS\user1 on a Windows host	Runs on a Windows host as BUSINESS\user1 Fails on a UNIX host: BUSINESS\user1 is not a valid UNIX user name
UNIX/Windows user account mapping is not enabled	—	user1 on a UNIX host	Fails on a Windows host: Windows requires a domain\user combination Runs on a UNIX host as user1
LSF_USER_DOMAIN= BUSINESS	lsf.conf	BUSINESS\user1 on a Windows host	Runs on a Windows host as BUSINESS\user1 Runs on a UNIX host as user1
LSF_USER_DOMAIN= BUSINESS	lsf.conf	user1 on a UNIX host	Runs on a Windows host as BUSINESS\user1 Runs on a UNIX host as user1
LSF_USER_DOMAIN= SUPPORT:ENGINEERING	lsf.conf	SUPPORT\user1 on a Windows host	Runs on a Windows host as SUPPORT\user1 Runs on a UNIX host as user1
LSF_USER_DOMAIN= SUPPORT:ENGINEERING	lsf.conf	BUSINESS\user1 on a Windows host	Runs on a Windows host as BUSINESS\user1 Fails on a UNIX host: LSF cannot strip the domain name, and BUSINESS\user1 is not a valid UNIX user name
LSF_USER_DOMAIN= SUPPORT:ENGINEERING	lsf.conf	user1 on a UNIX host	Runs on a Windows host as SUPPORT\user1; if the job cannot run with those credentials, the job runs as ENGINEERING\user1 Runs on a UNIX host as user1