Administering Platform LSF - SAS

Customizing Cross-Platform Signal Conversion
Default signal conversion
Custom signal conversion
Chapter 31
Configuring Job Controls
LSF supports signal conversion between UNIX and Windows for remote
interactive execution through RES.
On Windows, the CTRL+C and CTRL+BREAK key combinations are treated as
signals for console applications (these signals are also called console control
actions).
LSF supports these two Windows console signals for remote interactive
execution. LSF regenerates these signals for user tasks on the execution host.
In a mixed Windows/UNIX environment, LSF has the following default
conversion between the Windows console signals and the UNIX signals:
Windows
CTRL+C
CTRL+BREAK
UNIX
SIGINT
SIGQUIT
For example, if you issue the lsrun or bsub -I commands from a Windows
console but the task is running on an UNIX host, pressing the CTRL+C keys
will generate a UNIX SIGINT signal to your task on the UNIX host. The
opposite is also true.
For lsrun (but not bsub -I), LSF allows you to define your own signal
conversion using the following environment variables:
◆ LSF_NT2UNIX_CLTRC
◆ LSF_NT2UNIX_CLTRB
For example:
◆ LSF_NT2UNIX_CLTRC=SIGXXXX
◆ LSF_NT2UNIX_CLTRB=SIGYYYY
Here, SIGXXXX/SIGYYYY are UNIX signal names such as SIGQUIT, SIGTINT,
etc. The conversions will then be: CTRL+C=SIGXXXX and
CTRL+BREAK=SIGYYYY.
If both LSF_NT2UNIX_CLTRC and LSF_NT2UNIX_CLTRB are set to the same
value (LSF_NT2UNIX_CLTRC=SIGXXXX and
LSF_NT2UNIX_CLTRB=SIGXXXX), CTRL+C will be generated on the Windows
execution host.
For bsub -I, there is no conversion other than the default conversion.
Administering Platform LSF 395