{"id":137964,"date":"2021-12-03T15:33:00","date_gmt":"2021-12-03T20:33:00","guid":{"rendered":"http:\/\/www.bu.edu\/tech\/?page_id=137964"},"modified":"2026-03-18T14:06:16","modified_gmt":"2026-03-18T18:06:16","slug":"submitting-jobs","status":"publish","type":"page","link":"https:\/\/www.bu.edu\/tech\/support\/research\/system-usage\/running-jobs\/submitting-jobs\/","title":{"rendered":"Submitting your Batch Job"},"content":{"rendered":"<h2>Content<\/h2>\n<ul>\n<li><a href=\"#BATCHOPTIONS\">How to Submit a Batch Job<\/a><\/li>\n<li><a href=\"#MODULE\">Software Versions and the Module Command<\/a><\/li>\n<li><a href=\"#job-options\">General Job Submission Directives<\/a><\/li>\n<li><a href=\"#job-resources\">Resource Usage and Limits<\/a><\/li>\n<li><a href=\"#ENV\">SGE Environment Variables<\/a><\/li>\n<\/ul>\n<h2 style=\"margin-bottom: 1.em; margin-top: 2.5em;\"><a id=\"BATCHOPTIONS\" name=\"BATCHOPTIONS\"><\/a>How to Submit a Batch Job<\/h2>\n<p>Non-interactive batch jobs are submitted with the <a href=\"http:\/\/scv.bu.edu\/scc_manpages\/qsub.txt\"><strong>qsub<\/strong><\/a> command. The general form of the command is:<\/p>\n<pre class=\"code-block\"><code><span class=\"prompt\">scc % <\/span><span class=\"command\">qsub <span class=\"placeholder\">[options] command [arguments]<\/span><\/span><\/code><\/pre>\n<p>For example, to submit the <code><span class=\"command\">printenv<\/span><\/code> command to the batch system, execute:<\/p>\n<pre class=\"code-block\"><code><span class=\"prompt\">scc % <\/span><span class=\"command\">qsub<\/span> -b y printenv\r\n<span class=\"output\">Your job <span class=\"placeholder\">#jobID<\/span> (\"printenv\") has been submitted<\/span><\/code><\/pre>\n<p>The option <code>-b y<\/code> tells the batch system that the following command is a binary executable. The output message of the <code><span class=\"command\">qsub<\/span><\/code> command will print the job ID, which you can use to <a href=\"..\/tracking-jobs\">monitor the job&#8217;s status<\/a> within the queue. While the job is running the batch system creates <em>stdout<\/em> and <em>stderr<\/em> files, which by default are created in the job&#8217;s working directory. These files are named after the job&#8217;s name with the extension ending in the job&#8217;s number, for the above example <code>printenv.o<span class=\"placeholder\">#jobID<\/span><\/code> and <code>printenv.e<span class=\"placeholder\">#jobID<\/span><\/code>. The first one will contain the output of the command and the second will have the list of warnings and\u00a0 errors, if any, that occurred while the job was running.<\/p>\n<p>When running a program that requires arguments and passes additional directives to the batch system, it becomes useful to save them in a script file and submit this script as an argument to the <code><span class=\"command\">qsub<\/span><\/code> command. For example, the following script <code>script.sh<\/code> will execute a simple python job:<\/p>\n<pre class=\"code-block\"><code>#!\/bin\/bash -l\r\n \r\n<span class=\"comment\"># program name or command and its options and arguments<\/span>\r\npython myscript.py\r\n<\/code><\/pre>\n<div class=\"highlight-yellow\"><b>Note:<\/b> To be processed correctly, the script must contain a blank line at the end of the file.<\/div>\n<p>To submit this <code>script.sh<\/code> file to the batch system, execute:<\/p>\n<pre class=\"code-block\"><code><span class=\"prompt\">scc % <\/span><span class=\"command\">qsub<\/span> script.sh\r\n<span class=\"output\">Your job <span class=\"placeholder\">#jobID<\/span> (\"script.sh\") has been submitted<\/span><\/code><\/pre>\n<p>For other batch script examples, please see <a href=\"https:\/\/www.bu.edu\/tech\/support\/research\/system-usage\/running-jobs\/batch-script-examples\/\">Batch Script Examples<\/a>.<\/p>\n<h2 style=\"margin-bottom: 1.em; margin-top: 2.5em;\"><a id=\"MODULE\" name=\"Module\"><\/a>Software Versions and the Module Command<\/h2>\n<p>To access software packages on the SCC you need to use a <code><span class=\"command\">module<\/span><\/code> command. For example, even though there is a systems version of Python, it is very old and does not contain any popular packages. To get access to newer versions of the software, please use <a href=\"https:\/\/www.bu.edu\/tech\/support\/research\/software-and-programming\/software-and-applications\/modules\/\">Modules<\/a>. When a <code><span class=\"command\">module<\/span><\/code> command is used in a bash script, the first line of the script must contain the &#8220;<code><span class=\"command\">-l<\/span><\/code>&#8221; option to ensure proper handling of the module command:<\/p>\n<pre class=\"code-block\"><code>#!\/bin\/bash -l\r\n \r\n<span class=\"comment\"># Specify the version of MATLAB to be used<\/span>\r\nmodule load matlab\/2021b\r\n\r\n<span class=\"comment\"># program name or command and its options and arguments<\/span>\r\nmatlab -nodisplay -nodesktop -singleCompThread -batch \"n=4, rand; exit\"<\/code><\/pre>\n<h2 style=\"margin-bottom: 1.em; margin-top: 2.5em;\"><a name=\"job-options\"><\/a>General Job Submission Directives<\/h2>\n<p>There are a number of directives (options) that the user can pass to the batch system. These directives can either be provided as arguments to the <code><span class=\"command\">qsub<\/span><\/code> command or embedded in the job script. In a script file the lines containing these directives begin with the symbols <code><b>#$<\/b><\/code> &#8211; here is an example:<\/p>\n<pre class=\"code-block\"><code>#!\/bin\/bash -l\r\n\r\n<span class=\"command\">#$<\/span> -P myproject       <span class=\"comment\"># Specify the SCC project name you want to use<\/span>\r\n<span class=\"command\">#$<\/span> -l h_rt=12:00:00   <span class=\"comment\"># Specify the hard time limit for the job<\/span>\r\n<span class=\"command\">#$<\/span> -N myjob           <span class=\"comment\"># Give job a name<\/span>\r\n<span class=\"command\">#$<\/span> -j y               <span class=\"comment\"># Merge the error and output streams into a single file\r\n<\/span>\r\n\r\nmodule load python3\/3.13.8\r\npython myscript.py\r\n<\/code><\/pre>\n<p>Below is the list of some of the most commonly used directives:<\/p>\n<table>\n<tbody>\n<tr>\n<td colspan=\"2\" style=\"padding: 7px; background-color: #2c6696; color: #ffffff; text-align: center; font-size: 120%;\">General Directives<\/td>\n<\/tr>\n<tr>\n<th style=\"background-color: #c9d5d7; text-align: center; box-shadow: none; border: 1px solid #97a1a4;\" width=\"20%\">Directive<\/th>\n<th style=\"background-color: #c9d5d7; text-align: center; box-shadow: none; border: 1px solid #97a1a4;\" width=\"80%\">Description<\/th>\n<\/tr>\n<\/tbody>\n<tbody>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\"><b>-l h_rt<\/b>=<em>hh:mm:ss<\/em><\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">Hard run time limit in <code><span class=\"placeholder\">hh:mm:ss<\/span><\/code> format. The default is 12 hours.<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\"><b>-P<\/b> <em>project_name<\/em><\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">Project to which this jobs is to be assigned. This directive is <b>mandatory<\/b> for all users associated with any Med.Campus project.<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\"><b>-N<\/b> <em>job_name<\/em><\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">Specifies the job name. The default is the script or command name.<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\"><b>-o<\/b> <em>outputfile<\/em><\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">File name for the stdout output of the job.<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\"><b>-e<\/b> <em>errfile<\/em><\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">File name for the stderr output of the job.<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\"><b>-j y<\/b><\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">Merge the error and output stream files into a single file.<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\"><b>-m<\/b> <em>b|e|a|s|n<\/em><\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">Controls when the batch system sends email to you. The possible values are &#8211; when the job begins (b), ends (e), is aborted (a), is suspended (s), or never (n) &#8211; default.<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\"><b>-M<\/b> <em>user_email<\/em><\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">Overwrites the default email address used to send the job report.<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\"><b>-V<\/b><\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">All current environment variables should be exported to the batch job.<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\"><b>-v<\/b> <em>env=value<\/em><\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">Set the runtime environment variable <code><span class=\"placeholder\">env<\/span><\/code> to <code><span class=\"placeholder\">value<\/span><\/code>.<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\"><b>-hold_jid<\/b> <em>job_list<\/em><\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">Setup job dependency list. <code><span class=\"placeholder\">job_list<\/span><\/code> is a comma separated list of job ids and\/or job names which must complete before this job can run. See <a href=\"https:\/\/www.bu.edu\/tech\/support\/research\/system-usage\/running-jobs\/advanced-batch\/\">Advanced Batch System Usage<\/a> for more information.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 style=\"margin-bottom: 1.em; margin-top: 2.5em;\"><a name=\"job-resources\"><\/a>Resource Usage and Limits<\/h2>\n<p>The Sun Grid Engine (SGE) allows a job to request specific <a href=\"https:\/\/www.bu.edu\/tech\/support\/research\/system-usage\/running-jobs\/resources-jobs\/\">SCC resources<\/a> necessary for a successful run, including a node with large memory, multiple CPUs, a specific queue, or a node with a specific architecture. The <a href=\"https:\/\/www.bu.edu\/tech\/support\/research\/computing-resources\/tech-summary\/\">Technical Summary<\/a> contains hardware configuration for all SCC nodes. The <a href=\"https:\/\/www.bu.edu\/tech\/support\/research\/system-usage\/running-jobs\/advanced-batch\/\">Advanced Batch System Usage<\/a> page contains examples of running jobs which require parallel environments (OMP, MPI, GPU).<\/p>\n<p>The following table lists the most commonly used options to request resources available on the SCC:<\/p>\n<table>\n<tbody>\n<tr>\n<td colspan=\"2\" style=\"padding: 7px; background-color: #2c6696; color: #ffffff; text-align: center; font-size: 120%;\">Directives to request SCC resources<\/td>\n<\/tr>\n<tr>\n<th style=\"background-color: #c9d5d7; text-align: center; box-shadow: none; border: 1px solid #97a1a4;\" width=\"30%\">Directive<\/th>\n<th style=\"background-color: #c9d5d7; text-align: center; box-shadow: none; border: 1px solid #97a1a4;\" width=\"70%\">Description<\/th>\n<\/tr>\n<\/tbody>\n<tbody>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\"><b>-l h_rt<\/b>=<em>hh:mm:ss<\/em><\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">Hard run time limit in <code><span class=\"placeholder\">hh:mm:ss<\/span><\/code> format. The default is 12 hours.<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\"><b>-l mem_per_core<\/b>=<em>#G<\/em><\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">Request a node that has at least this amount of memory per core. Recommended choices are: 3G, 4G, 6G, 8G, 12G, 16G, 18G and 28G<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\"><b>-pe omp<\/b> <em>N<\/em><\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">Request multiple slots for Shared Memory applications (OpenMP, pthread). This option can also be used to reserve a larger amount of memory for the application. <code><span class=\"placeholder\">N<\/span><\/code> can vary. Currently, to request multiple cores on SCC&#8217;s shared nodes, we recommend selecting 1-4, 8, 16, 28, or 36 cores.<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\"><b>-pe mpi_#_tasks_per_node<\/b> <em>N<\/em><\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">Select multiple nodes for an MPI job. Number of tasks can be 4, 8, 12, 16, or 28 and <code><span class=\"placeholder\">N<\/span><\/code> must be a multiple of this value. See <a href=\"https:\/\/www.bu.edu\/tech\/support\/research\/system-usage\/running-jobs\/parallel-batch\/\">Running Parallel Batch Jobs<\/a> for more information.<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\"><b>-t <\/b> <em>N<\/em><\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">Submit an Array Job with <code><span class=\"placeholder\">N<\/span><\/code> tasks. N can be up to 75,000. For more information see <a href=\"https:\/\/www.bu.edu\/tech\/support\/research\/system-usage\/running-jobs\/advanced-batch\/#array\">Array Jobs<\/a><\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\"><b>-l cpu_arch<\/b>=<em>ARCH<\/em><\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">Select a processor architecture (broadwell, ivybridge, cascadelake&#8230;). See the <a href=\"https:\/\/www.bu.edu\/tech\/support\/research\/computing-resources\/tech-summary\/\">Technical Summary<\/a> for all available choices.<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\"><b>-l cpu_type<\/b>=<em>TYPE<\/em><\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">Select a processor type (X5670, X5675, Gold-6132 etc.) See the <a href=\"https:\/\/www.bu.edu\/tech\/support\/research\/computing-resources\/tech-summary\/\">Technical Summary<\/a> for all available choices.<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\"><b>-l gpus<\/b>=<em>G<\/em><\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">Requests a node with GPUs. <em>G <\/em>is the number of GPUs. See <a href=\"https:\/\/www.bu.edu\/tech\/support\/research\/software-and-programming\/programming\/multiprocessor\/gpu-computing\/\">GPU Computing<\/a> for more information.<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\"><b>-l gpu_type<\/b>=<em>GPUMODEL<\/em><\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">See <a href=\"#QGPUS\">below<\/a> on running the <code><span class=\"placeholder\">qgpus<\/span><\/code> command for current values. See the <a href=\"https:\/\/www.bu.edu\/tech\/support\/research\/software-and-programming\/programming\/multiprocessor\/gpu-computing\/\">GPU Computing<\/a> for more information.<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\"><b>-l gpu_c<\/b>=<em>CAPABILITY<\/em><\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">Specify the <strong>minimum<\/strong> GPU capability. See <a href=\"#QGPUS\">below<\/a> on running the <code><span class=\"placeholder\">qgpus<\/span><\/code> command for current values.<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\"><b>-l gpu_memory<\/b>=#G<\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">Request a node with a GPU that has at least the specified amount of memory in gigabytes. See <a href=\"#QGPUS\">below<\/a> on running the <code><span class=\"placeholder\">qgpus<\/span><\/code> command for current values.<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\"><b>-l avx<\/b><\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">Request a node that supports AVX and newer <a href=\"https:\/\/www.bu.edu\/tech\/support\/research\/software-and-programming\/programming\/compilers\/cpu-architectures\/\">CPU instructions<\/a>. A small number of modules require support for these instructions.<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\"><b>-l avx2<\/b><\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">Request a node that supports AVX2 and newer <a href=\"https:\/\/www.bu.edu\/tech\/support\/research\/software-and-programming\/programming\/compilers\/cpu-architectures\/\">CPU instructions<\/a>. A small number of modules require support for these instructions.<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\"><b>-l avx512<\/b><\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">Request a node that supports AVX512 and newer <a href=\"https:\/\/www.bu.edu\/tech\/support\/research\/software-and-programming\/programming\/compilers\/cpu-architectures\/\">CPU instructions<\/a>. As there are a number of generations of AVX-512 instructions this flag indicates the presence of the ones introduced by the Skylake architecture. A small number of modules require support for these instructions.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><a id=\"QGPUS\" name=\"QGPUS\"><\/a><\/p>\n<h4>Using the <code><span class=\"placeholder\">qgpus<\/span><\/code> command<\/h4>\n<p><code><span class=\"placeholder\">qgpus<\/span><\/code> is a utility that can be run on the SCC to show the GPUs currently installed on the SCC and their availability. To see the list of GPU types just run the command without any arguments. Adding the &#8220;<code><span class=\"command\">-s<\/span><\/code>&#8221; flag will show only those GPUs that are part of the shared queues. <\/p>\n<pre class=\"code-block\"><code><span class=\"prompt\">scc % <\/span><span class=\"command\">qgpus<\/span>\r\n<span class=\"output\">gpu_type  total  in_use  available\r\n--------  -----  ------  ---------\r\nA100          5      0      5\r\nA100-80G     24     17      7\r\nA40          68     15     48\r\nA6000        77     27     50\r\nH200         16     16      0\r\n...etc...<\/code><\/pre>\n<p>Run the command with the &#8220;<code><span class=\"command\">-v<\/span><\/code>&#8221; flag to see the GPU compute capability, GPU memory, the number of CPU cores installed on the GPU nodes, and the queue assignment. This can also be combined with the &#8220;<code><span class=\"command\">-s<\/span><\/code>&#8221; flag to limit the results to the shared queues. An additional flag, &#8220;<code><span class=\"command\">-q queuename<\/span><\/code>&#8220;, can be specified to view the GPU configuration for a particular queue.  <\/p>\n<pre class=\"code-block\"><code><span class=\"prompt\">scc % <\/span><span class=\"command\">qgpus -v<\/span>\r\n<span class=\"output\">host      gpu_type  gpu_c  gpu_mem  cpu_   cpu_    gpu_   gpu_    gpu_   queue_list\r\n                                    total  in_use  total  in_use  avail\r\n--------  --------  -----  -------  -----  ------  -----  ------  -----  ------------------------------\r\nscc-212   A100      8.0    80G      32     16      4      3       1      a100\r\nscc-211   A40       8.6    48G      32     18      4      4       0      a40\r\nscc-a03   H200      9.0    144G     32     17      4      4       0      h200\r\nscc-a04   H200      9.0    144G     32     13      4      4       0      h200\r\n...etc...<\/code><\/pre>\n<p>The following table summarizes the wall-clock runtime limits for different jobs based on their type:<\/p>\n<table width=\"300\">\n<tbody>\n<tr>\n<td colspan=\"2\" style=\"padding: 7px; background-color: #2c6696; color: #ffffff; text-align: center; font-size: 120%;\">Run time limits for shared nodes<\/td>\n<\/tr>\n<tr>\n<th style=\"background-color: #c9d5d7; text-align: center; box-shadow: none; border: 1px solid #97a1a4;\" width=\"30%\">Type of the job<\/th>\n<th style=\"background-color: #c9d5d7; text-align: center; box-shadow: none; border: 1px solid #97a1a4;\" width=\"70%\">Time limit on shared nodes<\/th>\n<\/tr>\n<\/tbody>\n<tbody>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\">Single processor job<\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">720 hours (30 days)<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\">OMP<\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">720 hours (30 days)<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\">MPI<\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">120 hours (5 days)<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\">GPU<\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">48 hours (2 days)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 style=\"margin-bottom: 1.em; margin-top: 2.5em;\"><a id=\"ENV\" name=\"ENV\"><\/a>SGE Environment Variables<\/h2>\n<p>When the job is scheduled to run, a number of environment variables are set and may be used by the program:<\/p>\n<table width=\"300\">\n<tbody>\n<tr>\n<td colspan=\"2\" style=\"padding: 7px; background-color: #2c6696; color: #ffffff; text-align: center; font-size: 120%;\">Batch System Environment<\/td>\n<\/tr>\n<tr>\n<th style=\"background-color: #c9d5d7; text-align: center; box-shadow: none; border: 1px solid #97a1a4;\" width=\"30%\">Environment Variable<\/th>\n<th style=\"background-color: #c9d5d7; text-align: center; box-shadow: none; border: 1px solid #97a1a4;\" width=\"70%\">Description<\/th>\n<\/tr>\n<\/tbody>\n<tbody>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\">JOB_ID<\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">Current job ID<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\">JOB_NAME<\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">Current job name<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\">NSLOTS<\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">The number of slots requested by a job<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\">HOSTNAME<\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">Name of execution host<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\">SGE_TASK_ID<\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">Array Job task index number<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\">SGE_TASK_STEPSIZE<\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">The step size of the array job specification<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\">SGE_TASK_FIRST<\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">The index number of the first array job task<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\">SGE_TASK_LAST<\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">The index number of the last array job task<\/td>\n<\/tr>\n<tr>\n<td style=\"padding: 7px; background-color: #ecf4f7; text-align: left; border: 1px solid #97a1a4;\">TMPDIR<\/td>\n<td style=\"padding: 7px; background-color: #ffffff; text-align: left; border: 1px solid #97a1a4;\">The absolute path to the job&#8217;s temporary working directory<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"<p>Content How to Submit a Batch Job Software Versions and the Module Command General Job Submission Directives Resource Usage and Limits SGE Environment Variables How to Submit a Batch Job Non-interactive batch jobs are submitted with the qsub command. The general form of the command is: scc % qsub [options] command [arguments] For example, to&#8230;<\/p>\n","protected":false},"author":1692,"featured_media":0,"parent":137962,"menu_order":1,"comment_status":"closed","ping_status":"closed","template":"","meta":[],"_links":{"self":[{"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/pages\/137964"}],"collection":[{"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/users\/1692"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/comments?post=137964"}],"version-history":[{"count":20,"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/pages\/137964\/revisions"}],"predecessor-version":[{"id":161269,"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/pages\/137964\/revisions\/161269"}],"up":[{"embeddable":true,"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/pages\/137962"}],"wp:attachment":[{"href":"https:\/\/www.bu.edu\/tech\/wp-json\/wp\/v2\/media?parent=137964"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}