G. UNIX/NT Mixed Clusters

The following points should be considered in a heterogeneous UNIX/NT environment.

• By default, LSF transfers environment variables from the submission to the execution host. However, some environment variables do not make sense when transferred. When submitting a job from Windows NT to a UNIX machine, the -L option of bsub can be used to reinitialize the environment variables. If submitting a job from a UNIX machine to an Windows NT machine, you can set the environment variables explicitly in your job script. Alternatively, a job starter can be used to reset the environment variables before starting the job.

LSF automatically resets the PATH on the execution host if the submission host is of a different type. If the submission host is Windows NT and the execution host is UNIX, the PATH variable is set to /bin:/usr/bin:/sbin:/usr/sbin and LSF_BINDIR (if defined in lsf.conf) is appended to it. If the submission host is UNIX and the execution host is Windows NT, the PATH variable is set to the system PATH variable with LSF_BINDIR appended to it. LSF looks for the presence of the WINDIR variable in the job's environment to determine whether the job was submitted from an Windows NT or UNIX host. If WINDIR is present, it is assumed that the submission host was Windows NT, otherwise the submission host is assumed to be a UNIX machine.

• The lssrvcntrl.exe binary only works when invoked from a Windows NT machine. You will not be able to start up LSF daemons on a Windows NT machine from a UNIX machine. The converse is also true: you cannot start the LSF daemons on a UNIX machine from a Windows NT machine.
• The LSF configuration files have to be accessible from both the Windows NT and UNIX machines. You need to set up a shared file system between the UNIX and Windows NT machines via NFS client on Windows NT or a SMB server on UNIX.

Alternatively, you can replicate the configuration files.