condor_ submit_dag is the program for submitting a DAG (directed
acyclic graph) of jobs for execution under Condor.
The program enforces the job dependencies defined
in one or more DAGInputFiles.
Each DAGInputFile contains commands
to direct the submission of jobs implied by the nodes
of a DAG to Condor.
See the Condor User Manual, section 2.11 for a complete
description.

Produce the Condor submit description file
for DAGMan, but do not submit DAGMan as a Condor job.

-verbose

Cause condor_ submit_dag
to give verbose error messages.

-force

Require condor_ submit_dag to overwrite
the files that it produces, if the files already exist. Note that
dagman.out will be appended to, not overwritten.

-maxidle NumberOfJobs

Sets the maximum number of idle
jobs allowed before condor_ dagman stops submitting more jobs. Once
idle jobs start to run, condor_ dagman will resume submitting jobs.
NumberOfJobs is a positive integer. If the option is
omitted, the number of idle jobs is unlimited.

-maxjobs NumberOfJobs

Sets the maximum number of jobs
within the DAG that will be submitted to Condor at one time.
NumberOfJobs is a positive integer. If the option is
omitted, the default number of jobs is unlimited.

-dagman DagmanExecutable

Allows the specification of an
alternate condor_ dagman executable to be used instead of the one found
in the user's path. This must be a fully qualified path.

-maxpre NumberOfPREscripts

Sets the maximum number of PRE
scripts within the DAG that may be running at one time.
NumberOfPREScripts is a positive integer. If this option is
omitted, the default number of PRE scripts is unlimited.

-maxpost NumberOfPOSTscripts

Sets the maximum number of
POST scripts within the DAG that may be running at one time.
NumberOfPOSTScripts is a positive integer. If this option is
omitted, the default number of POST scripts is unlimited.

-log LogFileName

Deprecated option; do not use.

-storklog LogFileName

Sets the file name for the
Stork log for data placement jobs.

-notification value

Sets the e-mail notification
for DAGMan itself. This information will be used within the Condor
submit description file for DAGMan. This file is produced by
condor_ submit_dag. See notification
within the section of submit description file commands in the
condor_ submit manual page on page
for specification of value.

-noeventchecks

This argument is no longer used; it
is now ignored. Its functionality is now implemented by
the DAGMAN_ALLOW_EVENTS configuration macro
(see section 3.3.22).

-allowlogerror

This optional argument has
condor_ dagman try to run the specified DAG, even in the case
of detected errors in the user log specification.

-r schedd_name

Submit to a remote schedd. The jobs
will be submitted to the schedd on the specified remote host. On Unix
systems, the Condor administrator for you site must override the default
AUTHENTICATION_METHODS configuration setting to enable remote file system
(FS_REMOTE) authentication.

-debug level

Passes the the level of debugging output desired to
condor_ dagman. level is an integer, with values of
0-7 inclusive, where 7 is the most verbose output.
A default value of 3 is passed to condor_ dagman when not
specified with this option.
See the
condor_ dagman manual page on page
for detailed descriptions of these values.

-usedagdir

This optional argument has causes
condor_ dagman to run each specified DAG as if condor_ submit_dag
had been run in the directory containing that DAG file. This option
is most useful when running multiple DAGs in a single condor_ dagman.

-outfile_dir directory

Specifies the directory in which the .dagman.out file will
be written. The directory may be specified relative to
the current working directory as condor_ submit_dag is executed,
or specified with an absolute path.
Without this option, the .dagman.out file is placed in the
same directory as the first DAG input file listed on the command line.

U.S. Government Rights Restrictions: Use, duplication, or disclosure
by the U.S. Government is subject to restrictions as set forth in
subparagraph (c)(1)(ii) of The Rights in Technical Data and Computer
Software clause at DFARS 252.227-7013 or subparagraphs (c)(1) and
(2) of Commercial Computer Software-Restricted Rights at 48 CFR
52.227-19, as applicable, Condor Team, Attention: Professor Miron
Livny, 7367 Computer Sciences, 1210 W. Dayton St., Madison,
WI 53706-1685, (608) 262-0856 or miron@cs.wisc.edu.