The bsub Command

You can also run a one-time Service batch submission with the bsub command:

bsub [ -name name ] [ -priority val ] [ -disc setting ] [ -mail address ] [ -stdin file ] [ -stdout file ] [ -stderr file ] [ -nfs ] [-RA] [-domain windowsdomain] [-noprompt] app [args...]

This submits a single Service, defined by app [args...], to be scheduled and run on the Grid. The arguments are as follows:

bsub Command Arguments

Argument

Description

name

Name of the Service.

priority

Priority of the Service.

disc

Indicates a name comparator value discriminator expression that must be satisfied to assign a Service or task to a node. For example, valid settings include os==win32 or cpuNo>=4. You can use this switch multiple times. Put quotes around parameters containing a greater-than or less-than symbol.

mail

Email address to send a confirmation message to when the Service is completed.

stdin

File to use as input for the Service. This setting is variable based on the -nfs switch, described below.

stdout

File to use as output when -nfs is enabled.

stderr

File to use as error output when -nfs is enabled.

nfs

Indicates whether inputs and outputs are available on a shared file system or whether you must stage them on the Manager. When enabled, -stdin, -stdout, and -stderr function as absolute locators for these files. When not enabled, -stdout and -stderr are ignored, and files designated as jobname.out and jobname.err are placed in the staging directory. When not enabled, -stdin refers to a file on the Driver file system which is to be staged on the Manager and retrieved by the Engine performing the Service.

RA

Runs the job on Engines as the current desktop user with the current Windows domain. PDriver first prompts for a password.

domain

Lets you specify a Windows Domain for Windows Engines to use when authenticating. This applies only when running PDriver from a UNIX machine.

noprompt

noprompt turns off the password prompt; this is useful only when Service RA auth is disabled on the Broker.

<app> [args...]

The application to run, and any optional arguments. The application is a binary or script on the Engine and found in the Engine’s path. args are any arguments passed to the application.

When you submit the Service, a batch ID is reported to the console. Use this ID when collecting outputs (when using the staging directory for input and output rather than NFS mounts.)