tssub

Submits a Terminal Services job to LSF.

Synopsis

tssub [bsub_options] command [arguments]

tssub [-h | -V]

Description

Submits a Terminal Services job for batch execution and assigns it a unique numerical job ID.

The tssub command is a wrapper around the bsub command that submits jobs only to hosts that have Microsoft Terminal Services installed. For bsub command options, see the bsub command.

You submit Terminal Services job with the tssub command instead of the bsub command. If the terminal window is closed, the job remains running. You can reconnect to view the job with the tspeek command.

The tssub command is supported on Windows and Linux. You cannot use the tssub command to submit Terminal Services jobs from UNIX.

If the job is dispatched to a host in which Terminal Services is not installed or properly configured, the job is set to the PEND state. A pending reason is written to the sbatchd.log.host_name file.

If the tssub -I command is specified, a terminal display is visible on the submission host after the job starts.

If the job is not a GUI job, LSF runs a command window and output is displayed in the command window when something is written to stdout.

Pre- and post-execution commands are run within the terminal session. The job does not complete until post-execution commands complete.

If you use the bjobs -l command to monitor the job, you see the following message:

"External Message 2 was posted from LSF\lsfadmin to message box 2"

The body of the message contains the ID of the terminal session that was created.

Use the tspeek command to view job output.

The tssub command sets the LSB_TSJOB and LSF_LOGON_DESKTOP environment variables. These variables are then transferred to the execution host:

LSF_LOGON_DESKTOP: When LSF_LOGON_DESKTOP=1, jobs run in interactive foreground sessions, and GUIs are displayed on the execution host. If this parameter is not defined, jobs run in the background.
LSB_TSJOB: When the LSB_TSJOB variable is defined to any value, it indicates to LSF that the job is a Terminal Services job.

Limitations

You cannot use the bmod command to modify a job that is submitted as a Terminal Services job to become a non-Terminal Services job.
The bsub -o out_file option is not supported for the tssub command.
Only Windows bsub command options are supported for the tssub command. For example, you cannot use the bsub options -Ip, -Is, -L login_shell with the tssub command.
Interactive bsub options (-I, -Ip, -Is) are not supported by the tssub command on Linux.
If user mapping is defined, the user who runs the tspeek command must have the required privileges to access the session.
LSF multicluster capability is not supported.

Options

bsub_options

Only Windows bsub options are supported for the tssub command. For example, you cannot use the bsub options -Ip, -Is, -L login_shell with the tssub command.

For bsub options, see the bsub command.

command [argument]

The job can be specified by a command line, or through the standard input if the command is not present on the command line. The command is assumed to begin with the first word that is not part of a tssub option. All arguments that follow command are provided as the arguments to the command.

The job command can be up to 4094 characters long for UNIX and Linux or up to 255 characters for Windows. If no job name is specified with the -J option, the bjobs, bhist, and bacct commands display the command as the job name.

The commands are run in the order in which they are given.

-h

Prints command usage to stderr and exits.

-V

Prints LSF release version to stderr and exits.