GLYPH<SM590000> Notify users. 

GLYPH<SM590000> Control scheduling and dispatch. 

GLYPH<SM590000> Specify resources and requirements. 

The simplest way to submit a job is to use the command-line options, as shown in Example 8-15. 

$ bsub -o %J.out -e %J.err -J 'omp_affinity' -q short './command' Job <212> is submitted to queue <short>. 

Example 8-15 shows some basic options of the bsub  command. The flags specify standard output ( -o ), input ( -i ), and error ( -e ) files. As shown in Example 8-15, -J  sets the job name, but it can also be used to submit multiple jobs (also know as an array of jobs ), and -q  sets the queue of which it can be a part. If the -q flag is not specified, the default queue is used (usually the normal  queue). The last option that is shown in Example 8-15 is the application to be run. 

Using the shell script is convenient when you must submit jobs regularly or that require many parameters. The file content that is shown in Example 8-16 is a regular shell script that embodies special comments (lines starts with #BSUB ) to control the behavior of the bsub command, and runs the noop  application by using the /bin/sh  interpreter. 

#!/bin/sh #BSUB -o %J.out -e %J.err #BSUB -J serial ./noop 

You can run the bsub myscript  or bsub < myscript commands to submit a script to IBM Spectrum LSF. In the first case, myscript  is not spooled, which means that changes on the script take effect if the job is still running. Conversely, bsub < myscrypt  (see Example 8-17) spools the script. 

$ bsub < noop_lsf.sh Job <220> is submitted to default queue <normal>. 

## Considerations for OpenMP programs 

You can use environment variables to control the running of OpenMP applications as described in 8.1.1, “Running OpenMP applications” on page 228. By default, the bsub command propagates all variables on the submitting host to the environment on the target machine. 

