The condor_submit_util makes the task of running jobs using the batch servers easier and more intuitive. condor_submit_util negotiates all job scheduling; it constructs the appropriate submit file for your job, and calls the condor_submit function. To use this utility you need a program to run. The format for using this script is:
In addition, the script can notify you when your job is done via email so you do not have to check the queue constantly using
condor_q. In future releases, the script also will be able to keep usage data so administrators can track overall performance.
The script can be run in two ways, interactively or from the command line. When running interactively, the script prompts you for the values required to run the batch job. If you supply arguments on the command line, these arguments are used in addition to default values for any values you do not supply.
Print help page and exit.
Print version information and exit.
Show information about what goes on during script execution.
Enter interactive mode, in which the script prompts you for the required values.
-s, --submitfile FILE
Specify the name of the created submit file (default is
Do not delete the created submit file.
Receive notification by email when jobs are complete.
-x, --executable FILE
The executable for condor to run (default is
-a, --arguments ARGS
Any arguments you want to pass to the executable (should be quoted, default is
-i, --input [FILE|PATT]
Either an explicit file name or base name of input files to the executable (default is
-o, --output [PATT]
Base name of output files for the executable (default is
-e, --error [PATT]
Base name of error files for the executable (default is
-l, --log [PATT]
Base name of log files for the executable (default is
-n, --iterations NUM
Number of iterations to submit (default is
Overwrite any existing files.
Use no input file for executable.
Send no arguments to executable.
You have a compiled executable (named foo) that takes a data set and does some analysis. You have five different data sets to run against (named data.0, data.1 ... data.4). You want to save the submit file and be notified when the job is done.
condor_submit_util -x foo -i "data" -k -N
You have an R program that has some random output. You want to run it 10 times to see the results.
condor_submit_util -i random.R -n 10
You have an R program that will take a long time to complete. You only need to run it once, but you want to be notified when it is done.
condor_submit_util -i long.R -n 1 -N
-l, these options are considered base names for the implied files. The actual file names are created with a numerical extension tied to its condor process number (0 indexed). This means that if you execute
condor_submit_util -o "out" -n 3, three output files named
out.2 are created.
-i, the script first checks to see if the name supplied is an actual file on disk, if not it uses the argument as a base name, similar to