Skip to main content

msub Commands

The following chart provides some of the more commonly used msub commands for use in either the job script or from the command line when using the University's high performance computing cluster, Quest.

Visit the msub website for additional information and #MSUB command options.

Script Command Line Description/Notes
#MSUB -a


Declares the time after which the job eligible for execution. Syntax: (brackets delimit optional items with the default being current date/time): [CC] [YY] [DD] hhmm[.SS]


-A account

Defines the account associated with the job.

#MSUB -d path

-d path

Specifies the directory in which the job should begin executing.

#MSUB -e filename

-e filename

Defines the file name to be used for stderr.

#MSUB -h


Put a user hold on the job at submission time.

#MSUB -j oe

-j oe

Combine stdout and stderr into the same output file. This is the default. If you want to give the combined stdout/stderr file a specific name, include the -o path flag also.

#MSUB -m option(s)

-m option(s)

Defines the set of conditions (a=abort, b=begin, e=end) when the server will send a mail message about the job to the user.

#MSUB -N name

-N name

Gives a user specified name to the job. Note that job names do not appear in all Moab job info displays, and do not determine how your jobs stdout/stderr files are named.

#MSUB -o filename

-o filename

Defines the file name to be sued for stdout. 

#MSUB -q queue
#MSUB -q queue@host

-q queue

Run the job in the specified queue (short, wide, debug, etc.).

#MSUB -S path

-S path

Specifies the shell which interprets the job script. The default is your login shell.

#MSUB -v list

-v list

Specifically adds a list (comma separated) of environment variables that are exported to the job.

#MSUB -v


Declares that all environment variables in the msub environment are exported to the batch job.



This option has been depreciated and should be ignored.

Last Updated: 26 July 2017

Get Help Back to top