$ jobsub -h
usage: jobsub [options] your_script [your_script_args]
submit your_script to local batch or to the OSG grid
--version show program's version number and exit
-h, --help show this help message and exit
-G ACCOUNTINGGROUP, --group=ACCOUNTINGGROUP
Group/Experiment/Subgroup for priorities and
-v, --verbose dump internal state of program (useful for debugging)
-M, --mail_always send mail when job completes or fails
send mail only when job fails due to error (default)
-Q, --mail_never never send mail (default is to send mail on error)
-T, --test_queue Submit as a test job. Job will run with highest
possible priority, but you can only have one such
job in the queue at a time.
-g, --grid run job on grid
--nowrapfile do not generate shell wrapper for fermigrid
operations. (default is to generate a wrapfile)
-c REQUIREMENTS, --condor_requirements=REQUIREMENTS
append condor requirements
-C execute on grid from directory you are currently in
-e ADDED_ENVIRONMENT, --environment=ADDED_ENVIRONMENT
export $envirionment variable to worker node
environment, can use this option as many times as
submit to different host
-p use parrot to run on afs (only makes sense with -a
--pOff turn parrot off explicitly (this is the default)
-n, --no_submit generate condor_command file but do not submit
--opportunistic submit opportunistically to Fermigrid GP Grid and CDF
Grid. This option will allow you to potentially get
more slots than your Fermigrid quota, but these slots
are subject to preemption
-N QUEUECOUNT submit N copies of this job. Each job will
have access to the environment variable
$PROCESS that provides the job number (0 to
<num>-1), equivalent to the decimal point in
the job ID (the '2' in 134567.2).
-x X509USERPROXY, --X509_USER_PROXY=X509USERPROXY
location of X509_USER_PROXY (expert mode)
-l LINES, --lines=LINES
[Expert option] Add the line <line> to the
Condor submission (.cmd) file. See Condor
help for more.
-a, --needafs run on afs using parrot (this is discouraged)
-L JOBLOGFILE, --log_file=JOBLOGFILE
Log file to hold log output from job.
--no_log_buffer write log file directly to disk. Default is to copy it
back after job is completed. This option is useful
for debugging but can be VERY DANGEROUS as joblogfile
typically is sent to bluearc. Using this option
incorrectly can cause all grid submission systems at
FNAL to become overwhelmed resulting in angry admins
hunting you down, so USE SPARINGLY.
--use_gftp use grid-ftp to transfer file back
-f INPUT_DIR_ARRAY -f <file> input file <file> will be copied to
$CONDOR_DIR_INPUT on the execution node.
Example :-f /grid/data/minerva/my/input/file.xxx
will be copied to $CONDOR_DIR_INPUT/file.xxx
Specify as many -f file1 -f file2 args as you need.
-d<tag> <dir> Writable directory $CONDOR_DIR_<tag>
exist on the execution node. After job completion,
its contents will be moved to <dir> automatically
Specify as many <tag>/<dir> pairs as you need.
SAM dataset definition used in a Directed Acyclic
optional project name for SAM DAG
Nova Specific Options:
--SMU steer jobs to HPC.SMU grid site
-i RELDIR release_directory for Nova Software
-t TESTRELDIR release_directory for test Nova Software
-r REL release_version for Nova Software
You can have as many instances of -c, -d, -e, -l and -y as you need.
The -d directory mapping works on non-Grid nodes, too.
More documentation is available at
and on this machine at