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.

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

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

tssub is supported on Windows and Linux. You cannot use tssub 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 and a pending reason is written in sbatchd.log.host_name.

If tssub -I is specified, a terminal display is visible on the submission host after the job has been started.

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 executed within the terminal session. The job does not complete until post-execution commands complete.

If you use bjobs -l to monitor the job, you see a message similar to “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 tspeek to view job output.

tssub 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. This allows GUIs to be 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 bmod to modify a job submitted as a Terminal Services job to become a non-Terminal Services job

  • The bsub option -o out_file is not supported for tssub

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

  • Interactive bsub options (-I, -Ip, -Is) are not supported with tssub on Linux

  • If user mapping is defined, the user who invokes tspeek must have the required privileges to access the session

  • MultiCluster is not supported

Options

bsub_options

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

For bsub options, see the bsub command.

command [argument]

The job can be specified by a command line argument command, 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 -J, bjobs, bhist and bacct displays the command as the job name.

The commands are executed 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.

See also

bsub, tspeek